[Desktop-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
got it, thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Triaged Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
No, this is only about removing it from container and cloud images. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Triaged Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 358147] Re: Wrong virtual desktop size setting set in xorg.conf
[Expired for screen-resolution-extra (Ubuntu) because there has been no activity for 60 days.] ** Changed in: screen-resolution-extra (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/358147 Title: Wrong virtual desktop size setting set in xorg.conf Status in screen-resolution-extra package in Ubuntu: Expired Bug description: Binary package hint: screen-resolution-extra In Jaunty (beta) on an Asus EeePC with a native LCD resolution of 800x480 When connecting a Dell E173FPB as an external monitor. Going into System > Preferences > Display and unchecking the 'cloned' checkbox it asks me if I want to add a virtual screen resolution as required by this option. It then asked me for my password and to log out. When I log out and back in the screen resolution settings do not allow the monitor to go above 800x600, even though the monitor's top resolution is 1280x1024. To solve this problem I edited the xorg.conf file and changed the virtual resolution setting from 800 1080 to 2048 2048. After logging out, this allowed me to select the correct resolution for the Dell monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/358147/+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 1987631] Re: Screencast only records one second
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1987631 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987711] Re: Ubuntu display get shifted after some time.
Thanks for the bug report. Please run these commands: journalctl -b0 > journal.txt xrandr --verbose > xrandr.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1987711 Title: Ubuntu display get shifted after some time. Status in xorg-server package in Ubuntu: Incomplete Bug description: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1987711/+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 1987711] Re: Ubuntu display get shifted after some time.
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1987711 Title: Ubuntu display get shifted after some time. Status in xorg-server package in Ubuntu: Incomplete Bug description: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1987711/+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 1987711] [NEW] Ubuntu display get shifted after some time.
You have been subscribed to a public bug: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- Ubuntu display get shifted after some time. https://bugs.launchpad.net/bugs/1987711 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- 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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
Is this means fwupd will also be removed from stock server image? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Triaged Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1987624] Re: Temporarily hold evolution-data-server in -proposed
** No longer affects: librest (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librest in Ubuntu. https://bugs.launchpad.net/bugs/1987624 Title: Temporarily hold evolution-data-server in -proposed Status in evolution-data-server package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: Maybe I needed to add more explicit Breaks in the packaging? But if evolution-data-server smoothly migrates, I fear that several packages including key ones like gnome-shell won't run because apps can't use both libsoup2 and libsoup3 in the same process. So I'm filing a blocker bug for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1987624/+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 1987631] Re: Screencast only records one second
I tested this on kinetic last night. For me the recorded video is valid but totem (Videos app) can't play it. I could play it with 'mpv' though. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987706] Re: [FFe] Should preinstall network-manager-openconnect-gnome
I'm setting this to Incomplete since the package isn't in main nor is the MIR process near completion. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1987706 Title: [FFe] Should preinstall network-manager-openconnect-gnome Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: The ubuntu-desktop package should recommend network-manager- openconnect-gnome, that is undergoing a main inclusion review (MIR) at bug #1986592. I believe this deserves a feature freeze exception because it adds support to UBuntu for several types of enterprise VPNs in wide use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1987706/+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 1987707] Re: [FFe] Should preinstall network-manager-openconnect-gnome
*** This bug is a duplicate of bug 1987706 *** https://bugs.launchpad.net/bugs/1987706 ** This bug has been marked a duplicate of bug 1987706 [FFe] Should preinstall network-manager-openconnect-gnome -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1987707 Title: [FFe] Should preinstall network-manager-openconnect-gnome Status in ubuntu-meta package in Ubuntu: New Bug description: The ubuntu-desktop package should recommend network-manager- openconnect-gnome, that is undergoing a main inclusion review (MIR) at bug #1986592. I believe this deserves a feature freeze exception because it adds support to Ubuntu for several types of enterprise VPNs in wide use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1987707/+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 1987411] Re: Drag and drop to Trash in sidebar not supported
According to the upstream comment this is a bug in GTK4/X11 and not Nautilus itself, which was addressed but not fully fixed in 4.7.2. A subsequent fix has been proposed for upstream GTK4: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4982 The workaround is to press "Shift" while doing the drag and drop to the Trash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1987411 Title: Drag and drop to Trash in sidebar not supported Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Couldn't find any mention in the upstream issues (https://gitlab.gnome.org/GNOME/nautilus/-/issues/?label_name%5B%5D=5.%20Drag- and-Drop) or whether this functionality is still WIP (https://gitlab.gnome.org/GNOME/nautilus/-/issues/2267), but drag and drop of files in Nautilus 43.beta.1 to its sidebar Trash gives the following error: Error while copying "[filename]". There was an error copying the file into trash:///. Operation not supported. The same error occurs if a file is right-click selected for copy and then going onto the Trash space and right-click for paste. ii gir1.2-nautilus-4.0:amd64 1:43~beta.1-2ubuntu1 amd64libraries for nautilus components - gir bindings ii libnautilus-extension4:amd64 1:43~beta.1-2ubuntu1 amd64libraries for nautilus components - runtime version ii nautilus 1:43~beta.1-2ubuntu1 amd64file manager and graphical shell for GNOME ii nautilus-data 1:43~beta.1-2ubuntu1 all data files for nautilus PRETTY_NAME="Ubuntu Kinetic Kudu (development branch)" NAME="Ubuntu" VERSION_ID="22.10" VERSION="22.10 (Kinetic Kudu)" VERSION_CODENAME=kinetic Windowing System: X11 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1987411/+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 1987624] Re: Temporarily hold evolution-data-server in -proposed
** Also affects: librest (Ubuntu) Importance: Undecided Status: New ** Changed in: librest (Ubuntu) Importance: Undecided => High ** Changed in: librest (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librest in Ubuntu. https://bugs.launchpad.net/bugs/1987624 Title: Temporarily hold evolution-data-server in -proposed Status in evolution-data-server package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in librest package in Ubuntu: Triaged Bug description: Maybe I needed to add more explicit Breaks in the packaging? But if evolution-data-server smoothly migrates, I fear that several packages including key ones like gnome-shell won't run because apps can't use both libsoup2 and libsoup3 in the same process. So I'm filing a blocker bug for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1987624/+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 1987707] Re: [FFe] Should preinstall network-manager-openconnect-gnome
** Description changed: The ubuntu-desktop package should recommend network-manager-openconnect- gnome, that is undergoing a main inclusion review (MIR) at bug #1986592. - I believe this deserves a feature freeze exception because it adds support to UBuntu for several types of - enterprise VPNs in wide use. + I believe this deserves a feature freeze exception because it adds + support to Ubuntu for several types of enterprise VPNs in wide use. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1987707 Title: [FFe] Should preinstall network-manager-openconnect-gnome Status in ubuntu-meta package in Ubuntu: New Bug description: The ubuntu-desktop package should recommend network-manager- openconnect-gnome, that is undergoing a main inclusion review (MIR) at bug #1986592. I believe this deserves a feature freeze exception because it adds support to Ubuntu for several types of enterprise VPNs in wide use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1987707/+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 1987706] [NEW] [FFe] Should preinstall network-manager-openconnect-gnome
Public bug reported: The ubuntu-desktop package should recommend network-manager-openconnect- gnome, that is undergoing a main inclusion review (MIR) at bug #1986592. I believe this deserves a feature freeze exception because it adds support to UBuntu for several types of enterprise VPNs in wide use. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1987706 Title: [FFe] Should preinstall network-manager-openconnect-gnome Status in ubuntu-meta package in Ubuntu: New Bug description: The ubuntu-desktop package should recommend network-manager- openconnect-gnome, that is undergoing a main inclusion review (MIR) at bug #1986592. I believe this deserves a feature freeze exception because it adds support to UBuntu for several types of enterprise VPNs in wide use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1987706/+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 1987707] [NEW] [FFe] Should preinstall network-manager-openconnect-gnome
Public bug reported: The ubuntu-desktop package should recommend network-manager-openconnect- gnome, that is undergoing a main inclusion review (MIR) at bug #1986592. I believe this deserves a feature freeze exception because it adds support to Ubuntu for several types of enterprise VPNs in wide use. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1987707 Title: [FFe] Should preinstall network-manager-openconnect-gnome Status in ubuntu-meta package in Ubuntu: New Bug description: The ubuntu-desktop package should recommend network-manager- openconnect-gnome, that is undergoing a main inclusion review (MIR) at bug #1986592. I believe this deserves a feature freeze exception because it adds support to Ubuntu for several types of enterprise VPNs in wide use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1987707/+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 1872124] Re: Please integrate ubuntu-drivers --gpgpu into Ubuntu Server
The version of subiquity in 22.04.1 supports this now. ** Changed in: subiquity Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1872124 Title: Please integrate ubuntu-drivers --gpgpu into Ubuntu Server Status in cloud-init: Incomplete Status in MAAS: Incomplete Status in subiquity: Fix Released Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Could subiquity provide an option in the UI to install and execute ubuntu-drivers-common on the target? The use case I'm interested in is an "on-rails" installation of Nvidia drivers for servers being installed for deep learning workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1872124/+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 1987624] Re: Temporarily hold evolution-data-server in -proposed
** Also affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Triaged ** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1987624 Title: Temporarily hold evolution-data-server in -proposed Status in evolution-data-server package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: Maybe I needed to add more explicit Breaks in the packaging? But if evolution-data-server smoothly migrates, I fear that several packages including key ones like gnome-shell won't run because apps can't use both libsoup2 and libsoup3 in the same process. So I'm filing a blocker bug for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1987624/+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 1987411] Re: Drag and drop to Trash in sidebar not supported
Thanks! ** Changed in: nautilus (Ubuntu) Status: New => Triaged ** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/2457 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1987411 Title: Drag and drop to Trash in sidebar not supported Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Couldn't find any mention in the upstream issues (https://gitlab.gnome.org/GNOME/nautilus/-/issues/?label_name%5B%5D=5.%20Drag- and-Drop) or whether this functionality is still WIP (https://gitlab.gnome.org/GNOME/nautilus/-/issues/2267), but drag and drop of files in Nautilus 43.beta.1 to its sidebar Trash gives the following error: Error while copying "[filename]". There was an error copying the file into trash:///. Operation not supported. The same error occurs if a file is right-click selected for copy and then going onto the Trash space and right-click for paste. ii gir1.2-nautilus-4.0:amd64 1:43~beta.1-2ubuntu1 amd64libraries for nautilus components - gir bindings ii libnautilus-extension4:amd64 1:43~beta.1-2ubuntu1 amd64libraries for nautilus components - runtime version ii nautilus 1:43~beta.1-2ubuntu1 amd64file manager and graphical shell for GNOME ii nautilus-data 1:43~beta.1-2ubuntu1 all data files for nautilus PRETTY_NAME="Ubuntu Kinetic Kudu (development branch)" NAME="Ubuntu" VERSION_ID="22.10" VERSION="22.10 (Kinetic Kudu)" VERSION_CODENAME=kinetic Windowing System: X11 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1987411/+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 1987678] Re: Update jansson 2.14 in jammy
Testing I did 1. I have built jansson 2.14 on all architecture in my personal PPA. https://launchpad.net/~hm-hui/+archive/ubuntu/sru-all/+packages 2. Verified the bug with a private package on arm64 platform on jammy and the bug gone after the package is rebuilt with jansson 2.14 in jammy. 3. Upgrade jansson to 2.14 on an amd64 desktop and performed some basic functions with network-manager without any issue. Also there aren't any interruption during upgrade/downgrade of jansson library 4. Use emacs to do some json file formatting and editing with jansson 2.14 installed. No issues discovered. ** Summary changed: - Update jansson 2.14 in jammy + Backport jansson 2.14 to jammy from kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jansson in Ubuntu. https://bugs.launchpad.net/bugs/1987678 Title: Backport jansson 2.14 to jammy from kinetic Status in jansson package in Ubuntu: New Bug description: [Impact] * jansson 2.13 has a symbol conflict with json-c library.(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966398 & https://github.com/akheron/jansson/issues/523). So an application is linking to both jansson and json-c, there will be 50% of chance that it reference to a wrong symbol, which need to SIGSEGV * In order to fix this issue, both json-c and jansson need to add symbol versioning. jansson library added this in 2.14(not yet in jammy) while json-c added in 0.15 (already in jammy) * And the affecting application should rebuild against the latest json-c and jansson libraries in order to have the correct symbol linked [Test Plan] * jansson is basically available in all of the cpu architecture. So the 1st test will be building in a personal ppa and see if it can be built in every platform. * Some of the library mentioned in the upstream issue checker can be used to verify the fix. But since I am working on a package in a private project which is hitting the issue. I am testing with my private packages(which is on arm64 platform) * Looking into the packages that depends on jansson. There are a large number of packages including network-manager. So I tried to pick 2 packages on my desktop to verify if there is regression 1. network-manager, since it is widely used in Ubuntu 2. emacs, since jansson is a JSON parser, so I pick an application that I can do some operation on JSON(e.g. formatting in emacs) [Where problems could occur] * jansson upstream is well maintained and there is also CI test job. jansson 2.14 is also packaged and maintained by Debian community. It is available for a few months already. So in general, the risk of regression is low in that perspective. * When looking into the changes between 2.13 and 2.14. There are changes in test coverage and some tidy up on the build scripts. The changes look safe but certainly there can be mistake and behaviour changes. But jansson do not depends on other packages and so this kind of regression on build script should be easily caught by test builds in different architecture and a simple integration test with package that depends on jansson. * On the library itself, it added symbol versioning to fix the bug and at the same time there are 3 new API added in 2.14. But these changes should be backward compatible. But since there is new symbols added, there can be new symbol conflict with other library but the impact should just be similar to the original bug that it is already conflict with json-c. There are alos misc fixes in like snprintf checking which looks to be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678/+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 1800634] Re: Mouse Movement Inverted
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1800634 Title: Mouse Movement Inverted Status in gnome-shell package in Ubuntu: Confirmed Status in iio-sensor-proxy package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm not sure this is gnome shell, as the behavior was also seen in GDM. Except in GDM, the entire screen was upside down in addition to the mouse being inverted. Upon login to gnome shell, the mouse pointer was upside down, and my movements on the mouse were inverted. Meaning when I moved my mouse up, the pointer went down (using an actual mouse, not a touchpad). I believe left and right worked properly (I can't remember clearly) But when I got the mouse over to the top-right of the screen to turn on wifi (NetworkManager was mysteriously not running -- solved by 'systemctl start NetworkManager' in a terminal), it actually opened up the gnome shell activities menu. Meaning that gnome-shell, at least from my interpretation, interpreted the click as being in the top-left of the screen instead of the top-right. I was able to finally open firefox (I had given up on mouse movement at this point and was using keyboard shortcuts) and googled the problem. I found this page: https://askubuntu.com/questions/1061403/ubuntu-18-04-1-upside-down- mouse-cursor-and-inverted-position I did an 'apt update' and 'apt full-upgrade', and then executed 'apt- get remove iio-sensor-proxy'. The reboot afterward took longer than usual it seemed, but it finally went down. Seeing that removing the iio-sensor-proxy worked, I was trying to figure out what sort of sensor would be triggering this behavior. And then I saw that I had my PS4 controller plugged in, which has the sixaxis sensor in it. Removing that package fixed the problem. My mouse/screen is no longer inverted, and my PS4 controller (which I'm assuming has the sensor) is still plugged in. 1) [joe@titan:~]$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 2) [joe@titan:~]$ apt-cache policy gnome-shell gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) I expected screen and mouse behavior to be normal. 4) Screen was upside down on GDM, but correct in gnome-shell. I'm not sure if the mouse movement was correct or upside down in GDM, typically I never touch my mouse during the login process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 06:33:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-10-27 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800634/+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 1800634] Re: Mouse Movement Inverted
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iio-sensor-proxy (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1800634 Title: Mouse Movement Inverted Status in gnome-shell package in Ubuntu: Confirmed Status in iio-sensor-proxy package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm not sure this is gnome shell, as the behavior was also seen in GDM. Except in GDM, the entire screen was upside down in addition to the mouse being inverted. Upon login to gnome shell, the mouse pointer was upside down, and my movements on the mouse were inverted. Meaning when I moved my mouse up, the pointer went down (using an actual mouse, not a touchpad). I believe left and right worked properly (I can't remember clearly) But when I got the mouse over to the top-right of the screen to turn on wifi (NetworkManager was mysteriously not running -- solved by 'systemctl start NetworkManager' in a terminal), it actually opened up the gnome shell activities menu. Meaning that gnome-shell, at least from my interpretation, interpreted the click as being in the top-left of the screen instead of the top-right. I was able to finally open firefox (I had given up on mouse movement at this point and was using keyboard shortcuts) and googled the problem. I found this page: https://askubuntu.com/questions/1061403/ubuntu-18-04-1-upside-down- mouse-cursor-and-inverted-position I did an 'apt update' and 'apt full-upgrade', and then executed 'apt- get remove iio-sensor-proxy'. The reboot afterward took longer than usual it seemed, but it finally went down. Seeing that removing the iio-sensor-proxy worked, I was trying to figure out what sort of sensor would be triggering this behavior. And then I saw that I had my PS4 controller plugged in, which has the sixaxis sensor in it. Removing that package fixed the problem. My mouse/screen is no longer inverted, and my PS4 controller (which I'm assuming has the sensor) is still plugged in. 1) [joe@titan:~]$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 2) [joe@titan:~]$ apt-cache policy gnome-shell gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) I expected screen and mouse behavior to be normal. 4) Screen was upside down on GDM, but correct in gnome-shell. I'm not sure if the mouse movement was correct or upside down in GDM, typically I never touch my mouse during the login process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 06:33:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-10-27 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800634/+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 1800634] Re: Mouse Movement Inverted
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1800634 Title: Mouse Movement Inverted Status in gnome-shell package in Ubuntu: Confirmed Status in iio-sensor-proxy package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm not sure this is gnome shell, as the behavior was also seen in GDM. Except in GDM, the entire screen was upside down in addition to the mouse being inverted. Upon login to gnome shell, the mouse pointer was upside down, and my movements on the mouse were inverted. Meaning when I moved my mouse up, the pointer went down (using an actual mouse, not a touchpad). I believe left and right worked properly (I can't remember clearly) But when I got the mouse over to the top-right of the screen to turn on wifi (NetworkManager was mysteriously not running -- solved by 'systemctl start NetworkManager' in a terminal), it actually opened up the gnome shell activities menu. Meaning that gnome-shell, at least from my interpretation, interpreted the click as being in the top-left of the screen instead of the top-right. I was able to finally open firefox (I had given up on mouse movement at this point and was using keyboard shortcuts) and googled the problem. I found this page: https://askubuntu.com/questions/1061403/ubuntu-18-04-1-upside-down- mouse-cursor-and-inverted-position I did an 'apt update' and 'apt full-upgrade', and then executed 'apt- get remove iio-sensor-proxy'. The reboot afterward took longer than usual it seemed, but it finally went down. Seeing that removing the iio-sensor-proxy worked, I was trying to figure out what sort of sensor would be triggering this behavior. And then I saw that I had my PS4 controller plugged in, which has the sixaxis sensor in it. Removing that package fixed the problem. My mouse/screen is no longer inverted, and my PS4 controller (which I'm assuming has the sensor) is still plugged in. 1) [joe@titan:~]$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 2) [joe@titan:~]$ apt-cache policy gnome-shell gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) I expected screen and mouse behavior to be normal. 4) Screen was upside down on GDM, but correct in gnome-shell. I'm not sure if the mouse movement was correct or upside down in GDM, typically I never touch my mouse during the login process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 06:33:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-10-27 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800634/+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 1987678] Re: Update jansson 2.14 in jammy
The attachment "jansson_kinetic.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jansson in Ubuntu. https://bugs.launchpad.net/bugs/1987678 Title: Update jansson 2.14 in jammy Status in jansson package in Ubuntu: New Bug description: [Impact] * jansson 2.13 has a symbol conflict with json-c library.(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966398 & https://github.com/akheron/jansson/issues/523). So an application is linking to both jansson and json-c, there will be 50% of chance that it reference to a wrong symbol, which need to SIGSEGV * In order to fix this issue, both json-c and jansson need to add symbol versioning. jansson library added this in 2.14(not yet in jammy) while json-c added in 0.15 (already in jammy) * And the affecting application should rebuild against the latest json-c and jansson libraries in order to have the correct symbol linked [Test Plan] * jansson is basically available in all of the cpu architecture. So the 1st test will be building in a personal ppa and see if it can be built in every platform. * Some of the library mentioned in the upstream issue checker can be used to verify the fix. But since I am working on a package in a private project which is hitting the issue. I am testing with my private packages(which is on arm64 platform) * Looking into the packages that depends on jansson. There are a large number of packages including network-manager. So I tried to pick 2 packages on my desktop to verify if there is regression 1. network-manager, since it is widely used in Ubuntu 2. emacs, since jansson is a JSON parser, so I pick an application that I can do some operation on JSON(e.g. formatting in emacs) [Where problems could occur] * jansson upstream is well maintained and there is also CI test job. jansson 2.14 is also packaged and maintained by Debian community. It is available for a few months already. So in general, the risk of regression is low in that perspective. * When looking into the changes between 2.13 and 2.14. There are changes in test coverage and some tidy up on the build scripts. The changes look safe but certainly there can be mistake and behaviour changes. But jansson do not depends on other packages and so this kind of regression on build script should be easily caught by test builds in different architecture and a simple integration test with package that depends on jansson. * On the library itself, it added symbol versioning to fix the bug and at the same time there are 3 new API added in 2.14. But these changes should be backward compatible. But since there is new symbols added, there can be new symbol conflict with other library but the impact should just be similar to the original bug that it is already conflict with json-c. There are alos misc fixes in like snprintf checking which looks to be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678/+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 1987411] Re: Drag and drop to Trash in sidebar not supported
I have opened an upstream report: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2457 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2457 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2457 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1987411 Title: Drag and drop to Trash in sidebar not supported Status in nautilus package in Ubuntu: New Bug description: Couldn't find any mention in the upstream issues (https://gitlab.gnome.org/GNOME/nautilus/-/issues/?label_name%5B%5D=5.%20Drag- and-Drop) or whether this functionality is still WIP (https://gitlab.gnome.org/GNOME/nautilus/-/issues/2267), but drag and drop of files in Nautilus 43.beta.1 to its sidebar Trash gives the following error: Error while copying "[filename]". There was an error copying the file into trash:///. Operation not supported. The same error occurs if a file is right-click selected for copy and then going onto the Trash space and right-click for paste. ii gir1.2-nautilus-4.0:amd64 1:43~beta.1-2ubuntu1 amd64libraries for nautilus components - gir bindings ii libnautilus-extension4:amd64 1:43~beta.1-2ubuntu1 amd64libraries for nautilus components - runtime version ii nautilus 1:43~beta.1-2ubuntu1 amd64file manager and graphical shell for GNOME ii nautilus-data 1:43~beta.1-2ubuntu1 all data files for nautilus PRETTY_NAME="Ubuntu Kinetic Kudu (development branch)" NAME="Ubuntu" VERSION_ID="22.10" VERSION="22.10 (Kinetic Kudu)" VERSION_CODENAME=kinetic Windowing System: X11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1987411/+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 1987678] Re: Update jansson 2.14 in jammy
debdiff with jammy which shows the diff from 2.13 to 2.14 ** Patch added: "jansson_jammy.debdiff" https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678/+attachment/5611682/+files/jansson_jammy.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jansson in Ubuntu. https://bugs.launchpad.net/bugs/1987678 Title: Update jansson 2.14 in jammy Status in jansson package in Ubuntu: New Bug description: [Impact] * jansson 2.13 has a symbol conflict with json-c library.(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966398 & https://github.com/akheron/jansson/issues/523). So an application is linking to both jansson and json-c, there will be 50% of chance that it reference to a wrong symbol, which need to SIGSEGV * In order to fix this issue, both json-c and jansson need to add symbol versioning. jansson library added this in 2.14(not yet in jammy) while json-c added in 0.15 (already in jammy) * And the affecting application should rebuild against the latest json-c and jansson libraries in order to have the correct symbol linked [Test Plan] * jansson is basically available in all of the cpu architecture. So the 1st test will be building in a personal ppa and see if it can be built in every platform. * Some of the library mentioned in the upstream issue checker can be used to verify the fix. But since I am working on a package in a private project which is hitting the issue. I am testing with my private packages(which is on arm64 platform) * Looking into the packages that depends on jansson. There are a large number of packages including network-manager. So I tried to pick 2 packages on my desktop to verify if there is regression 1. network-manager, since it is widely used in Ubuntu 2. emacs, since jansson is a JSON parser, so I pick an application that I can do some operation on JSON(e.g. formatting in emacs) [Where problems could occur] * jansson upstream is well maintained and there is also CI test job. jansson 2.14 is also packaged and maintained by Debian community. It is available for a few months already. So in general, the risk of regression is low in that perspective. * When looking into the changes between 2.13 and 2.14. There are changes in test coverage and some tidy up on the build scripts. The changes look safe but certainly there can be mistake and behaviour changes. But jansson do not depends on other packages and so this kind of regression on build script should be easily caught by test builds in different architecture and a simple integration test with package that depends on jansson. * On the library itself, it added symbol versioning to fix the bug and at the same time there are 3 new API added in 2.14. But these changes should be backward compatible. But since there is new symbols added, there can be new symbol conflict with other library but the impact should just be similar to the original bug that it is already conflict with json-c. There are alos misc fixes in like snprintf checking which looks to be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678/+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 1699942] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1699942 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1699942 Title: network-manager fails to deprecate addresses Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: network manager does not properly deprecate autoconfigured temporary IP addresses when ValidLifetime for a prefix is 0 in router advertisements. This behaviour is non-compliant with RFC 4861 § 6.3.4, which reads: If the prefix is already present in the host's Prefix List as the result of a previously received advertisement, reset its invalidation timer to the Valid Lifetime value in the Prefix Information option. If the new Lifetime value is zero, time-out the prefix immediately. The hosts instead continued to use temporary addresses configured until they reached their timeout, rather than immediately dropping the addresses. It further appears that it is generating new temporary addresses when the previous ones expire, but I have not been monitoring hosts closely enough to tell for sure---I will update on this when I have further information. This problem was discovered on Ubuntu Studio 16.04.2; it is not present on Ubuntu Server (which uses Debian networking scripts). Additional Info: $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1987678] [NEW] Update jansson 2.14 in jammy
Public bug reported: [Impact] * jansson 2.13 has a symbol conflict with json-c library.(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966398 & https://github.com/akheron/jansson/issues/523). So an application is linking to both jansson and json-c, there will be 50% of chance that it reference to a wrong symbol, which need to SIGSEGV * In order to fix this issue, both json-c and jansson need to add symbol versioning. jansson library added this in 2.14(not yet in jammy) while json-c added in 0.15 (already in jammy) * And the affecting application should rebuild against the latest json-c and jansson libraries in order to have the correct symbol linked [Test Plan] * jansson is basically available in all of the cpu architecture. So the 1st test will be building in a personal ppa and see if it can be built in every platform. * Some of the library mentioned in the upstream issue checker can be used to verify the fix. But since I am working on a package in a private project which is hitting the issue. I am testing with my private packages(which is on arm64 platform) * Looking into the packages that depends on jansson. There are a large number of packages including network-manager. So I tried to pick 2 packages on my desktop to verify if there is regression 1. network-manager, since it is widely used in Ubuntu 2. emacs, since jansson is a JSON parser, so I pick an application that I can do some operation on JSON(e.g. formatting in emacs) [Where problems could occur] * jansson upstream is well maintained and there is also CI test job. jansson 2.14 is also packaged and maintained by Debian community. It is available for a few months already. So in general, the risk of regression is low in that perspective. * When looking into the changes between 2.13 and 2.14. There are changes in test coverage and some tidy up on the build scripts. The changes look safe but certainly there can be mistake and behaviour changes. But jansson do not depends on other packages and so this kind of regression on build script should be easily caught by test builds in different architecture and a simple integration test with package that depends on jansson. * On the library itself, it added symbol versioning to fix the bug and at the same time there are 3 new API added in 2.14. But these changes should be backward compatible. But since there is new symbols added, there can be new symbol conflict with other library but the impact should just be similar to the original bug that it is already conflict with json-c. There are alos misc fixes in like snprintf checking which looks to be safe. ** Affects: jansson (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jansson in Ubuntu. https://bugs.launchpad.net/bugs/1987678 Title: Update jansson 2.14 in jammy Status in jansson package in Ubuntu: New Bug description: [Impact] * jansson 2.13 has a symbol conflict with json-c library.(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966398 & https://github.com/akheron/jansson/issues/523). So an application is linking to both jansson and json-c, there will be 50% of chance that it reference to a wrong symbol, which need to SIGSEGV * In order to fix this issue, both json-c and jansson need to add symbol versioning. jansson library added this in 2.14(not yet in jammy) while json-c added in 0.15 (already in jammy) * And the affecting application should rebuild against the latest json-c and jansson libraries in order to have the correct symbol linked [Test Plan] * jansson is basically available in all of the cpu architecture. So the 1st test will be building in a personal ppa and see if it can be built in every platform. * Some of the library mentioned in the upstream issue checker can be used to verify the fix. But since I am working on a package in a private project which is hitting the issue. I am testing with my private packages(which is on arm64 platform) * Looking into the packages that depends on jansson. There are a large number of packages including network-manager. So I tried to pick 2 packages on my desktop to verify if there is regression 1. network-manager, since it is widely used in Ubuntu 2. emacs, since jansson is a JSON parser, so I pick an application that I can do some operation on JSON(e.g. formatting in emacs) [Where problems could occur] * jansson upstream is well maintained and there is also CI test job. jansson 2.14 is also packaged and maintained by Debian community. It is available for a few months already. So in general, the risk of regression is low in that perspective. * When looking into the changes between 2.13 and 2.14. There are changes in test coverage and some tidy up on the build scripts. The changes look safe but certainly there can be mistake and behaviour changes. But jansson do
[Desktop-packages] [Bug 1987678] Re: Update jansson 2.14 in jammy
debdiff with kinetic which shows it is a simple rebuild in jammy ** Patch added: "jansson_kinetic.debdiff" https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678/+attachment/5611681/+files/jansson_kinetic.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jansson in Ubuntu. https://bugs.launchpad.net/bugs/1987678 Title: Update jansson 2.14 in jammy Status in jansson package in Ubuntu: New Bug description: [Impact] * jansson 2.13 has a symbol conflict with json-c library.(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966398 & https://github.com/akheron/jansson/issues/523). So an application is linking to both jansson and json-c, there will be 50% of chance that it reference to a wrong symbol, which need to SIGSEGV * In order to fix this issue, both json-c and jansson need to add symbol versioning. jansson library added this in 2.14(not yet in jammy) while json-c added in 0.15 (already in jammy) * And the affecting application should rebuild against the latest json-c and jansson libraries in order to have the correct symbol linked [Test Plan] * jansson is basically available in all of the cpu architecture. So the 1st test will be building in a personal ppa and see if it can be built in every platform. * Some of the library mentioned in the upstream issue checker can be used to verify the fix. But since I am working on a package in a private project which is hitting the issue. I am testing with my private packages(which is on arm64 platform) * Looking into the packages that depends on jansson. There are a large number of packages including network-manager. So I tried to pick 2 packages on my desktop to verify if there is regression 1. network-manager, since it is widely used in Ubuntu 2. emacs, since jansson is a JSON parser, so I pick an application that I can do some operation on JSON(e.g. formatting in emacs) [Where problems could occur] * jansson upstream is well maintained and there is also CI test job. jansson 2.14 is also packaged and maintained by Debian community. It is available for a few months already. So in general, the risk of regression is low in that perspective. * When looking into the changes between 2.13 and 2.14. There are changes in test coverage and some tidy up on the build scripts. The changes look safe but certainly there can be mistake and behaviour changes. But jansson do not depends on other packages and so this kind of regression on build script should be easily caught by test builds in different architecture and a simple integration test with package that depends on jansson. * On the library itself, it added symbol versioning to fix the bug and at the same time there are 3 new API added in 2.14. But these changes should be backward compatible. But since there is new symbols added, there can be new symbol conflict with other library but the impact should just be similar to the original bug that it is already conflict with json-c. There are alos misc fixes in like snprintf checking which looks to be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
** Tags removed: rls-kk-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Triaged Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1699942] Re: network-manager fails to deprecate addresses
We believe the kernel handles RAs itself, adding a task for it. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1699942 Title: network-manager fails to deprecate addresses Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: network manager does not properly deprecate autoconfigured temporary IP addresses when ValidLifetime for a prefix is 0 in router advertisements. This behaviour is non-compliant with RFC 4861 § 6.3.4, which reads: If the prefix is already present in the host's Prefix List as the result of a previously received advertisement, reset its invalidation timer to the Valid Lifetime value in the Prefix Information option. If the new Lifetime value is zero, time-out the prefix immediately. The hosts instead continued to use temporary addresses configured until they reached their timeout, rather than immediately dropping the addresses. It further appears that it is generating new temporary addresses when the previous ones expire, but I have not been monitoring hosts closely enough to tell for sure---I will update on this when I have further information. This problem was discovered on Ubuntu Studio 16.04.2; it is not present on Ubuntu Server (which uses Debian networking scripts). Additional Info: $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1248260] Re: ibus-daemon hogging resources
Experiencing something like this on 22.04 LTS after upgrading from 20.04 LTS - I'm running KUbuntu. So far I'm seeing a direct relation with chrome browser (Version 104.something, supposedly the latest). As soon as I invoke Chrome, after a short while keyboard responsiveness becomes extremely lagged to a point of not being usable at all. Semi WORK-AROUND: -I select restart from the iBus language selection indicator panel - the indicator in question does not re-appear, but the ibus-daemon process disappears clearing the keyboard lag from all applications. Still some system-wide input fields stop accepting input like Dolphin, KDE menu, and possibly a few others. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1248260 Title: ibus-daemon hogging resources Status in ibus package in Ubuntu: Confirmed Bug description: At times, typing becomes very sluggish and I can see ibus-daemon becomes the process consuming most CPU and most memory in the system. Everything else is responsive, i.e. mouse ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 17:08:06 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2010-07-07 (1217 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True SourcePackage: ibus UpgradeStatus: Upgraded to saucy on 2013-10-25 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1248260/+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 1987665] Re: The "Settings" app is missing the 'Appearance' option
I tried to use ubuntu-bug to report the lock up of chrome during the ubuntu-bug reporting process but ubuntu-bug won't allow a report on ubuntu-bug itself. bill@bill ~$ ubuntu-bug ubuntu-bug dpkg-query: no packages found matching ubuntu-bug FYI - When I attempted to report the bug this page is about the first time, the ubuntu-bug output on the terminal showed the following if that's any help: bill@bill ~$ ubuntu-bug ubuntu-settings bill@bill ~$ [75943:75943:0825/071203.322589:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported. Opening in existing browser session. You guys should use ubuntu-bug to report something and attempt to add an attachment as I did and you might see the chrome lock up yourselves. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1987665 Title: The "Settings" app is missing the 'Appearance' option Status in ubuntu-settings package in Ubuntu: New Bug description: In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine. Ubuntu Forum users report they have an Appearance option in their Settings app; I don't. bill@bill ~$ apt show ubuntu-settings Package: ubuntu-settings Version: 22.04.6 Priority: optional Section: x11 Origin: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1987665/+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 1974449] Re: No filepicker in Firefox with enforced AppArmor profile
Upgraded to `firefox/jammy 104.0+build2-0ubuntu0.22.04.1~mt1`
After a quick testing (removing site-specific configurations for
`usr.bin.firefox` + apparmor service force-reload'ed) I can confirm that the
implemented fix works for me.
Thank you all, especially thanks to Oliver Tilloy.
** Changed in: firefox (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1974449
Title:
No filepicker in Firefox with enforced AppArmor profile
Status in firefox package in Ubuntu:
Fix Released
Status in firefox source package in Bionic:
Fix Released
Status in firefox source package in Focal:
Fix Released
Bug description:
# System
Ubuntu 22.04 LTS (Jammy Jellyfish) {kubuntu-ppa/backports/ubuntu jammy main |
mozillateam/ppa/ubuntu/ jammy main}
Package: firefox
Version: 100.0.1+build1-0ubuntu0.22.04.1~mt1
---
# Description
I’m using Firefox stand-alone package (not the mainline Ubuntu Snap version)
under KDE (native KDE filepicker) with enforced `usr.bin.firefox AppArmor`
profile (included in `firefox` package) and when I try to open a file, save a
screenshot or print to file, no filepicker shown.
---
# Error message
Can't open portal file chooser:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy
prevents this sender from sending this message to this recipient;
type="method_call", […] interface="org.freedesktop.portal.FileChooser"
member="OpenFile" […] destination="org.freedesktop.portal.Desktop" […])
---
# Suggested fix
Please see commit:
https://github.com/snapcore/snapd/pull/8793/files/ec7f01e8c15bf9303cfb30354470d2a7b3783f25
# Fix result
Implementing the part for `org.freedesktop.portal.Desktop` from the above
commit resolves the filepicker issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1974449/+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 1987001] Re: netplan.io autopkgtest failures with NetworkManager 1.39.90
** Changed in: network-manager (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1987001 Title: netplan.io autopkgtest failures with NetworkManager 1.39.90 Status in NetworkManager: Unknown Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Committed Bug description: netplan.io's autopkgtests are failing with NetworkManager 1.40 RC1 (1.39.90). https://autopkgtest.ubuntu.com/packages/n/netplan.io/kinetic/amd64 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-40/NEWS log excerpt: == FAIL: test_bond_mode_8023ad_adselect (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", line 147, in test_bond_mode_8023ad_adselect self.assertEqual(f.read().strip(), 'bandwidth 1') AssertionError: 'stable 0' != 'bandwidth 1' - stable 0 + bandwidth 1 == FAIL: test_bond_mode_balance_tlb_learn_interval (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", line 670, in test_bond_mode_balance_tlb_learn_interval self.assertEqual(f.read().strip(), '15') AssertionError: '1' != '15' - 1 + 15 ? + To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1987001/+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 1987665] Re: The "Settings" app is missing the 'Appearance' option
I tried to attach an image to this report AFTER the report was already accepted and chrome locked up immediately after I selected a file. That's the second lock up when selecting a file. ** Attachment added: "Settings.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1987665/+attachment/5611652/+files/Settings.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1987665 Title: The "Settings" app is missing the 'Appearance' option Status in ubuntu-settings package in Ubuntu: New Bug description: In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine. Ubuntu Forum users report they have an Appearance option in their Settings app; I don't. bill@bill ~$ apt show ubuntu-settings Package: ubuntu-settings Version: 22.04.6 Priority: optional Section: x11 Origin: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1987665/+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 1987665] [NEW] The "Settings" app is missing the 'Appearance' option
Public bug reported: In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine. Ubuntu Forum users report they have an Appearance option in their Settings app; I don't. bill@bill ~$ apt show ubuntu-settings Package: ubuntu-settings Version: 22.04.6 Priority: optional Section: x11 Origin: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1987665 Title: The "Settings" app is missing the 'Appearance' option Status in ubuntu-settings package in Ubuntu: New Bug description: In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine. Ubuntu Forum users report they have an Appearance option in their Settings app; I don't. bill@bill ~$ apt show ubuntu-settings Package: ubuntu-settings Version: 22.04.6 Priority: optional Section: x11 Origin: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1987665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1734371 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+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 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
BTW: I succeed in my test and I checked my working ACR38 AC1038-based Smart Card Reader with these commands: # apt install libacsccid1 pcscd pcsc-tools opensc # pcsc_scan and in FF snap I cannot load /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so (thanks to https://guide.debianizzati.org/index.php/Carta_Nazionale/Regionale_dei_Servizi) I don't know the relation between libacsccid1 and opensc but I suppose that libacsccid1 is a library used by pcscd, whereas opensc is a middleware between FF (or other PKCS11 API software) and pcscd. I would like to try packaging pcsc-tools as a SNAP to see if it can read card info, do you think it could be a good idea, or just a waste of time? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967632/+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 1987001] Re: netplan.io autopkgtest failures with NetworkManager 1.39.90
Upstream is working on a solution. ** Changed in: network-manager (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1987001 Title: netplan.io autopkgtest failures with NetworkManager 1.39.90 Status in NetworkManager: Unknown Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: In Progress Bug description: netplan.io's autopkgtests are failing with NetworkManager 1.40 RC1 (1.39.90). https://autopkgtest.ubuntu.com/packages/n/netplan.io/kinetic/amd64 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-40/NEWS log excerpt: == FAIL: test_bond_mode_8023ad_adselect (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", line 147, in test_bond_mode_8023ad_adselect self.assertEqual(f.read().strip(), 'bandwidth 1') AssertionError: 'stable 0' != 'bandwidth 1' - stable 0 + bandwidth 1 == FAIL: test_bond_mode_balance_tlb_learn_interval (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", line 670, in test_bond_mode_balance_tlb_learn_interval self.assertEqual(f.read().strip(), '15') AssertionError: '1' != '15' - 1 + 15 ? + To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1987001/+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 1987001] Re: netplan.io autopkgtest failures with NetworkManager 1.39.90
Done: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1072 (I might not have the time to follow through with this, though) ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1072 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1072 ** Also affects: network-manager via https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1072 Importance: Unknown Status: Unknown ** Changed in: netplan.io (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1987001 Title: netplan.io autopkgtest failures with NetworkManager 1.39.90 Status in NetworkManager: Unknown Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Triaged Bug description: netplan.io's autopkgtests are failing with NetworkManager 1.40 RC1 (1.39.90). https://autopkgtest.ubuntu.com/packages/n/netplan.io/kinetic/amd64 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-40/NEWS log excerpt: == FAIL: test_bond_mode_8023ad_adselect (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", line 147, in test_bond_mode_8023ad_adselect self.assertEqual(f.read().strip(), 'bandwidth 1') AssertionError: 'stable 0' != 'bandwidth 1' - stable 0 + bandwidth 1 == FAIL: test_bond_mode_balance_tlb_learn_interval (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", line 670, in test_bond_mode_balance_tlb_learn_interval self.assertEqual(f.read().strip(), '15') AssertionError: '1' != '15' - 1 + 15 ? + To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1987001/+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 1987648] [NEW] error in makedocs.py (zziplib-0.13.62)
Public bug reported: ./configure --with-zlib=/usr/local --prefix=/libs/zziplib-0.13.72 --enable-enable-default-aclocaldir=/usr/local/share/aclocal --enable- enable-default-pkgconfigdir=/usr/local/lib/pkgconfig PYTHONDONTWRITEBYTECODE=1 /usr/bin/python ../../docs/makedocs.py ../../zzip/*.c \ "--package=zziplib" "--version=0.13.62" \ "--onlymainheader=zzip/lib.h" "--output=zziplib" File "../../docs/makedocs.py", line 40 print t_fileheader.get_filename(), t_fileheader.src_mainheader() ** Affects: zziplib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zziplib in Ubuntu. https://bugs.launchpad.net/bugs/1987648 Title: error in makedocs.py (zziplib-0.13.62) Status in zziplib package in Ubuntu: New Bug description: ./configure --with-zlib=/usr/local --prefix=/libs/zziplib-0.13.72 --enable-enable-default-aclocaldir=/usr/local/share/aclocal --enable- enable-default-pkgconfigdir=/usr/local/lib/pkgconfig PYTHONDONTWRITEBYTECODE=1 /usr/bin/python ../../docs/makedocs.py ../../zzip/*.c \ "--package=zziplib" "--version=0.13.62" \ "--onlymainheader=zzip/lib.h" "--output=zziplib" File "../../docs/makedocs.py", line 40 print t_fileheader.get_filename(), t_fileheader.src_mainheader() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zziplib/+bug/1987648/+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 1987411] Re: Drag and drop to Trash in sidebar not supported
Thanks, any chance you would report the issue upstream on gitlab? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1987411 Title: Drag and drop to Trash in sidebar not supported Status in nautilus package in Ubuntu: New Bug description: Couldn't find any mention in the upstream issues (https://gitlab.gnome.org/GNOME/nautilus/-/issues/?label_name%5B%5D=5.%20Drag- and-Drop) or whether this functionality is still WIP (https://gitlab.gnome.org/GNOME/nautilus/-/issues/2267), but drag and drop of files in Nautilus 43.beta.1 to its sidebar Trash gives the following error: Error while copying "[filename]". There was an error copying the file into trash:///. Operation not supported. The same error occurs if a file is right-click selected for copy and then going onto the Trash space and right-click for paste. ii gir1.2-nautilus-4.0:amd64 1:43~beta.1-2ubuntu1 amd64libraries for nautilus components - gir bindings ii libnautilus-extension4:amd64 1:43~beta.1-2ubuntu1 amd64libraries for nautilus components - runtime version ii nautilus 1:43~beta.1-2ubuntu1 amd64file manager and graphical shell for GNOME ii nautilus-data 1:43~beta.1-2ubuntu1 all data files for nautilus PRETTY_NAME="Ubuntu Kinetic Kudu (development branch)" NAME="Ubuntu" VERSION_ID="22.10" VERSION="22.10 (Kinetic Kudu)" VERSION_CODENAME=kinetic Windowing System: X11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1987411/+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 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
https://launchpad.net/~liuck You can test your reader/card with OpenSC without firefox. see: "man pkcs11-tool" or "pkcs11-tool --help". "pkcs11-tool --test --login" will try and read certificates and do sign/verify using private keys. It may prompt for pin several times. If you can also add --module to use test a different PKCS11 module. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967632/+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 1987411] Re: Drag and drop to Trash in sidebar not supported
A different error for the same drag and drop issue is also saying: The target doesn't support symbolic links. ** Attachment added: "Error while creating link to "filename"." https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1987411/+attachment/5611623/+files/symlink.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1987411 Title: Drag and drop to Trash in sidebar not supported Status in nautilus package in Ubuntu: New Bug description: Couldn't find any mention in the upstream issues (https://gitlab.gnome.org/GNOME/nautilus/-/issues/?label_name%5B%5D=5.%20Drag- and-Drop) or whether this functionality is still WIP (https://gitlab.gnome.org/GNOME/nautilus/-/issues/2267), but drag and drop of files in Nautilus 43.beta.1 to its sidebar Trash gives the following error: Error while copying "[filename]". There was an error copying the file into trash:///. Operation not supported. The same error occurs if a file is right-click selected for copy and then going onto the Trash space and right-click for paste. ii gir1.2-nautilus-4.0:amd64 1:43~beta.1-2ubuntu1 amd64libraries for nautilus components - gir bindings ii libnautilus-extension4:amd64 1:43~beta.1-2ubuntu1 amd64libraries for nautilus components - runtime version ii nautilus 1:43~beta.1-2ubuntu1 amd64file manager and graphical shell for GNOME ii nautilus-data 1:43~beta.1-2ubuntu1 all data files for nautilus PRETTY_NAME="Ubuntu Kinetic Kudu (development branch)" NAME="Ubuntu" VERSION_ID="22.10" VERSION="22.10 (Kinetic Kudu)" VERSION_CODENAME=kinetic Windowing System: X11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1987411/+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 1987646] [NEW] incorrect configure options (zziplib-0.13.62)
Public bug reported:
First:
Line 14515
# Check whether --enable-enable-default-pkgconfigdir was given.
if test "${enable_enable_default_pkgconfigdir+set}" = set; then :
enableval=$enable_enable_default_pkgconfigdir;
fi
Line 14769
# Check whether --enable-enable-default-aclocaldir was given.
if test "${enable_enable_default_aclocaldir+set}" = set; then :
enableval=$enable_enable_default_aclocaldir;
fi
but --help says:
--enable-default-pkgconfigdir(=PATH) override the libdir/pkgconfig default
--enable-default-aclocaldir(=PATH) override the datadir/aclocal default
and with parameter --enable-default ... configure says "configure:
WARNING: unrecognized options: --enable-default-aclocaldir, --enable-
default-pkgconfigdir"
Second:
configure cannot find /usr/bin/python3
but works after sudo ln -s /usr/bin/python3 /usr/bin/python
Please add to search python3
** Affects: zziplib (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zziplib in Ubuntu.
https://bugs.launchpad.net/bugs/1987646
Title:
incorrect configure options (zziplib-0.13.62)
Status in zziplib package in Ubuntu:
New
Bug description:
First:
Line 14515
# Check whether --enable-enable-default-pkgconfigdir was given.
if test "${enable_enable_default_pkgconfigdir+set}" = set; then :
enableval=$enable_enable_default_pkgconfigdir;
fi
Line 14769
# Check whether --enable-enable-default-aclocaldir was given.
if test "${enable_enable_default_aclocaldir+set}" = set; then :
enableval=$enable_enable_default_aclocaldir;
fi
but --help says:
--enable-default-pkgconfigdir(=PATH) override the libdir/pkgconfig default
--enable-default-aclocaldir(=PATH) override the datadir/aclocal default
and with parameter --enable-default ... configure says "configure:
WARNING: unrecognized options: --enable-default-aclocaldir, --enable-
default-pkgconfigdir"
Second:
configure cannot find /usr/bin/python3
but works after sudo ln -s /usr/bin/python3 /usr/bin/python
Please add to search python3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zziplib/+bug/1987646/+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 1377891] Re: ibus-x11 crashed with SIGSEGV in __run_exit_handlers()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1377891 Title: ibus-x11 crashed with SIGSEGV in __run_exit_handlers() Status in ibus package in Ubuntu: Confirmed Bug description: aplication crashed immediately after start-up, window with fault occured aprox 10times ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 Uname: Linux 3.16.0-031600-generic x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 6 12:15:47 2014 ExecutablePath: /usr/lib/ibus/ibus-x11 InstallationDate: Installed on 2014-08-19 (47 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon ProcEnviron: LANGUAGE=cs PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fb2e52e54fd <__run_exit_handlers+61>: mov (%rcx),%r8 PC (0x7fb2e52e54fd) ok source "(%rcx)" (0x36ec3ce0) not located in a known VMA region (needed readable region)! destination "%r8" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: __run_exit_handlers (status=1, listp=0x7fb2e56696c8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:54 __GI_exit (status=) at exit.c:104 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: ibus-x11 crashed with SIGSEGV in __run_exit_handlers() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1377891/+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 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
This problem is an Ubuntu/snap packaging issue. FF and Thunderbird both allow the loading of PKCS11 modules as do other programs. But the snap has not packaged these. Access to smartcards is usually handled by PC/SC i.e. the pcscd daemon. It provides locking access to the smartcards from multiple running applications. So this is another issue for snap, how to provide access to this system daemon. Snap does provide the ability to load the p11-kit but then p11-kit tries to load other PKCS11 modules which may need to load additional libraries. /usr/lib/x86_64-linux-gnu/pkcs11/* and run "p11-kit list- modules". p11-kit has a client/remote capability that I have never looked at. It might be possible to use this from snap to a "remote" server running on the the local host. Are there FF extensions that may similar problems? Until Ubuntu can packaged up other pkcs11 modules and handle pcscd, the way to: "test from CLI if my smart card reader is working" is to use the debian firefox-esr which does not have any problems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967632/+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 1961495] Re: Update adwaita-icon-theme to 42~beta-1
I've merged the packaging, but I think we need to improve our filters because we're still leaving uninstalled icons around... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adwaita-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1961495 Title: Update adwaita-icon-theme to 42~beta-1 Status in adwaita-icon-theme package in Ubuntu: Triaged Bug description: There were multiple bugs filed in Debian because of missing icons. More investigation is needed. This isn't an important update for 22.04 LTS because we're shipping a lot of GNOME 41 apps anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1961495/+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 1987631] Re: Screencast only records one second
Deleting .cache/gstreamer-1.0 doesn't change anything. The bug you mention also seems to be a different one because I get a video, it is just very choppy. The upstream bug fix i shared also doesn't seem to help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
Look like a temporary fix for the bug landed in upstream with https://gitlab.gnome.org/skeller/gnome- shell/-/commit/398b1c6c79da0bb0630ab7448cd227d85c3985eb#249ab328def8cba907309a9d7c0ddf940776c578. I will test if this also fixes the bug for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
Sounds like this might be bug 1963264 so please try: cd ~/.cache rm -rf gstreamer-1.0 ** Tags added: kinetic ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5585 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1954970] Re: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"
I don't think remmina will be updated to 1.27 (1.26 would be enough). Usually the version of the package remain the same, only some patches get applied when needed. Browsers are exempt from that rule. Ubuntu maintainers might cherry pick this: https://gitlab.com/Remmina/Remmina/-/merge_requests/2402/diffs?commit_id=ecfa4fe4a93f99fd8991eb18fc1442c01b642a07 but they must be convinced this is a issue for enough people to do that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1954970 Title: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Status in freerdp2 package in Ubuntu: Incomplete Status in freerdp2 source package in Jammy: Incomplete Bug description: Xubuntu Jammy (21.04) after upgrade libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) Remmina can't connect to any RDP server (Win2008 R2) with error: "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Rollback to Impish version of libs libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2 makes it work normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1954970/+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 1987628] Re: Xwayland fails to start on Xilinx: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane
And to Debian: https://salsa.debian.org/xorg-team/wayland/xwayland/-/merge_requests/2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1987628 Title: Xwayland fails to start on Xilinx: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane Status in xwayland package in Ubuntu: In Progress Bug description: Xwayland fails to start on Xilinx: /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane This is particularly important since it prevents gnome-shell from starting Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1987628/+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 1987631] [NEW] Screencast only records one second
Public bug reported: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in gnome-shell package in Ubuntu: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+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 1423773] Re: [memory leak] Gnome-Shell don't free ram when changing the wallpaper
I encountered the same issue, but visible through open file handles in Fedora. Every time the desktop background is changed with gsettings, a filehandle is opened that is never closed. I filed a bug report with gnome: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5796 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5796 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5796 -- 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/1423773 Title: [memory leak] Gnome-Shell don't free ram when changing the wallpaper Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Incomplete Bug description: Sorry for my bad english, here is the link to see the error by yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1423773/+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 1987628] Re: Xwayland fails to start on Xilinx: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane
Proposed fix: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/946 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1987628 Title: Xwayland fails to start on Xilinx: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane Status in xwayland package in Ubuntu: In Progress Bug description: Xwayland fails to start on Xilinx: /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane This is particularly important since it prevents gnome-shell from starting Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1987628/+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 1987628] [NEW] Xwayland fails to start on Xilinx: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane
Public bug reported: Xwayland fails to start on Xilinx: /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane This is particularly important since it prevents gnome-shell from starting Wayland sessions. ** Affects: xwayland (Ubuntu) Importance: High Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: jammy wayland wayland-session xilinx ** Description changed: Xwayland fails to start on Xilinx: /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane This is particularly important since it prevents gnome-shell from - starting. + starting Wayland sessions. ** Tags added: wayland wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1987628 Title: Xwayland fails to start on Xilinx: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane Status in xwayland package in Ubuntu: In Progress Bug description: Xwayland fails to start on Xilinx: /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane This is particularly important since it prevents gnome-shell from starting Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1987628/+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 1987624] [NEW] Temporarily hold evolution-data-server in -proposed
Public bug reported: Maybe I needed to add more explicit Breaks in the packaging? But if evolution-data-server smoothly migrates, I fear that several packages including key ones like gnome-shell won't run because apps can't use both libsoup2 and libsoup3 in the same process. So I'm filing a blocker bug for now. ** Affects: evolution-data-server (Ubuntu) Importance: Critical Status: Triaged ** Tags: block-proposed kinetic ** Changed in: evolution-data-server (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1987624 Title: Temporarily hold evolution-data-server in -proposed Status in evolution-data-server package in Ubuntu: Triaged Bug description: Maybe I needed to add more explicit Breaks in the packaging? But if evolution-data-server smoothly migrates, I fear that several packages including key ones like gnome-shell won't run because apps can't use both libsoup2 and libsoup3 in the same process. So I'm filing a blocker bug for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1987624/+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 1987579] Re: "Remove Hyperlink" feature causes text duplication and corruption when removing email hyperlinks inside angle brackets
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1987579 Title: "Remove Hyperlink" feature causes text duplication and corruption when removing email hyperlinks inside angle brackets Status in libreoffice package in Ubuntu: Confirmed Bug description: This may be the single weirdest bug report I've ever made. Steps to Reproduce: 1: Open LibreOffice Calc. 2: In any cell of the spreadsheet, type: The email address placed inside the angle brackets can be whatever you want, but the angle brackets are necessary for the bug to surface (at least usually). 3: Press Enter. The email address will automatically be turned into a hyperlink. 4: Right-click the automatically created hyperlink, and click "Remove Hyperlink". Expected result: The actual text of the cell should remain unchanged, but the hyperlink itself should be removed. Actual result: The text within the cell morphs into the following: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987579/+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 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
https://launchpad.net/~dengert , https://launchpad.net/~tnetter unfortunately my summary of @dengert instructions is nor a solution / nor a workaround. Following those steps I managed to add only one "security device", but it does not work when accessing the website: https://dichiarazioneprecompilatasc.agenziaentrate.gov.it/ The security device I have added uses the module /usr/share/bit4id/x/libbit4xpki.so (FF copies it to /run/user/1000/doc/fb1650f7/libbit4xpki.so) I didn't succeed in adding: /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so (FF copies it to /run/user/1000/doc/bc62d73/opensc-pkcs11.so but issues "Cannot load module") I am not in a urgent need of this bug to be fixed, but I'd really like to help in finding the root cause. I am wondering if there is a small shell/python script that can be helpful to isolate the problem avoiding to reproduce the steps with Firefox that hides details. For example: how can I test from CLI if my smart card reader is working with OpenSC? (keeping out SNAP or Firefox from the test?) I think it can be useful to write down here a simple check. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967632/+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 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
Uploaded the SRU as well now ** Changed in: gnome-control-center (Ubuntu Jammy) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: gnome-control-center (Ubuntu Jammy) Assignee: (unassigned) => Dirk Su (dirksu) -- 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/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. [Other info] This patch is from upstream gnome-control-center. For more information refer to https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1388 The patch also adds some new user visible strings, those will be translatable on launchpad and initially displayed in english but we can get translations updated then as part of the next language packs refresh To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1983645/+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 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
** Description changed: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. [Other info] - This patch is from upstream gnome-control-center. For more information + This patch is from upstream gnome-control-center. For more information refer to https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1388 + + The patch also adds some new user visible strings, those will be + translatable on launchpad and initially displayed in english but we can + get translations updated then as part of the next language packs refresh -- 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/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. [Other info] This patch is from upstream gnome-control-center. For more information refer to https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1388 The patch also adds some new user visible strings, those will be translatable on launchpad and initially displayed in english but we can get translations updated then as part of the next language packs refresh To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1983645/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
upstream believes the gtk4 version in kinetic should resolve the issue ** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: New Status in gtk+3.0 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gtk/issues/2457 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+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 1987134] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver
** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: New => Incomplete -- 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/1987134 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: Incomplete Bug description: An Nvidia driver upgrade in Ubuntu 20.04 caused waking from S3 suspend to lead to a black screen. Upgrading to Ubuntu 22.04 using latest stable Nvidia driver 515.65.01 did not resolve the issue. There are several Nvidia sleep tickets that at first seem related, but mention dmesg entries that I am not seeing which makes me suspect I have a different issue: * https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970088 * https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303 Workaround dhenry mentions in 1970088 of disabling the nvidia suspend and hibernate systemd services makes no difference for me. Currrently running Ubuntu 22.04, Nvidia GTX 970 on driver 515.65.01, AMD Ryzen 7 5800X. Here are journalctl excerpts during the reboot process, with and without nvidia systemd suspend services. dmesg and /var/log/kern.log show no errors as are mentioned in the above tickets. With disabled nvidia suspend systemd services: Aug 19 12:42:37 uf-panacea ModemManager[2731]: [sleep-monitor] system is about to suspend Aug 19 12:42:37 uf-panacea NetworkManager[2617]: [1660938157.8491] manager: NetworkManager state> Aug 19 12:42:37 uf-panacea systemd[1]: Reached target Sleep. Aug 19 12:42:37 uf-panacea systemd[1]: Starting Record successful boot for GRUB... Aug 19 12:42:37 uf-panacea systemd[1]: Starting System Suspend... Aug 19 12:42:37 uf-panacea systemd-sleep[13048]: Entering sleep state 'suspend'... Aug 19 12:42:37 uf-panacea systemd[1]: grub-common.service: Deactivated successfully. Aug 19 12:42:37 uf-panacea systemd[1]: Finished Record successful boot for GRUB. With enabled nvidia suspend systemd services: Aug 19 12:12:25 uf-panacea systemd[1]: Starting NVIDIA system suspend actions... Aug 19 12:12:25 uf-panacea suspend[15998]: nvidia-suspend.service Aug 19 12:12:25 uf-panacea logger[15998]: <13>Aug 19 12:12:25 suspend: nvidia-suspend.service Aug 19 12:12:25 uf-panacea systemd[1]: grub-common.service: Deactivated successfully. Aug 19 12:12:25 uf-panacea systemd[1]: Finished Record successful boot for GRUB. Aug 19 12:12:25 uf-panacea systemd[1]: Starting GRUB failed boot detection... Aug 19 12:12:25 uf-panacea systemd[1]: grub-initrd-fallback.service: Deactivated successfully. Aug 19 12:12:25 uf-panacea systemd[1]: Finished GRUB failed boot detection. Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "40" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event1 - Power Button: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "43" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event0 - Power Button: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "44" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event4 - USB Mouse OKLIC: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "45" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event5 - USB Mouse OKLIC Mouse: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "46" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event6 - USB Mouse OKLIC System Control: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "47" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event7 - USB Mouse OKLIC Consumer Control: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "53" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "53" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event11 - Valve Software Steam Controller: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "50" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "50" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event9 - Logitech G305: device removed Aug 19 12:12:25 uf-panacea rtkit-daemon[3286]: Supervising 10 threads of 4 processes of 1 users. Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "51" Aug 19 12:12:25 uf-panacea
[Desktop-packages] [Bug 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
Hi Canonical team, One of the OEM was requesting regarding the libqmi > libqmi: fa6c7a97 Not like the commit ID you shared for MM and libmibm, the libqmi commit ID is not a version bump commit, can we use a911f6874493a0e6a567cecf4582584312cd8d23? or the next version bump? Please do share if you have any further inputs. Thanks and Best Regards, Murali -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+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 1987572] Re: Segfault due to libpython3.10
Thank you for your bug report but please report PopOS bugs to them and not on Ubuntu, we have no idea what sort of changes they carry in their packages ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1987572 Title: Segfault due to libpython3.10 Status in nautilus package in Ubuntu: Invalid Bug description: ``` $ lsb_release -rd Description: Pop!_OS 22.04 LTS Release: 22.04 ``` ``` $ apt-cache policy nautilus nautilus: Installed: 1:42.2-0ubuntu1 Candidate: 1:42.2-0ubuntu1 Version table: *** 1:42.2-0ubuntu1 500 500 http://apt.pop-os.org/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://apt.pop-os.org/ubuntu jammy/main amd64 Packages ``` I expected Nautilus to open properly, but got a segfault instead when running: ``` $ nautilus ``` It seems related to LibPython (output for `journalctl -q | grep -i nautilus`): ``` Aug 25 00:12:59 pop-os kernel: nautilus[15964]: segfault at 58 ip 7fe281475052 sp 7ffd24384d48 error 4 in libpython3.10.so.1.0[7fe28145f000+22d000] Aug 25 00:15:23 pop-os kernel: nautilus[16160]: segfault at 10 ip 7f90d352e68f sp 7ffdcba0d3c0 error 4 in libpython3.10.so.1.0[7f90d346d000+2b5000] Aug 25 00:17:26 pop-os kernel: nautilus[17395]: segfault at 58 ip 7f5e34675052 sp 7fff94fc3d18 error 4 in libpython3.10.so.1.0[7f5e3465f000+22d000] Aug 25 00:26:32 pop-os sudo[22071]: fee : TTY=pts/1 ; PWD=/home/fee ; USER=root ; COMMAND=/usr/bin/apt install --reinstall nautilus Aug 25 00:26:35 pop-os tracker-extract[22122]: Could not get mimetype, Error when getting information for file “/usr/share/applications/nautilus-autorun-software.desktop.dpkg-new”: No such file or directory Aug 25 00:26:35 pop-os tracker-extract[22122]: Task for 'file:///usr/share/applications/nautilus-autorun-software.desktop.dpkg-new' finished with error: Error when getting information for file “/usr/share/applications/nautilus-autorun-software.desktop.dpkg-new”: No such file or directory Aug 25 00:26:35 pop-os tracker-extract[22122]: Could not get mimetype, Error when getting information for file “/usr/share/applications/nautilus-autorun-software.desktop.dpkg-tmp”: No such file or directory Aug 25 00:26:35 pop-os tracker-extract[22122]: Task for 'file:///usr/share/applications/nautilus-autorun-software.desktop.dpkg-tmp' finished with error: Error when getting information for file “/usr/share/applications/nautilus-autorun-software.desktop.dpkg-tmp”: No such file or directory Aug 25 00:26:35 pop-os tracker-extract[22122]: Could not get mimetype, Error when getting information for file “/usr/share/applications/org.gnome.Nautilus.desktop.dpkg-new”: No such file or directory Aug 25 00:26:35 pop-os tracker-extract[22122]: Task for 'file:///usr/share/applications/org.gnome.Nautilus.desktop.dpkg-new' finished with error: Error when getting information for file “/usr/share/applications/org.gnome.Nautilus.desktop.dpkg-new”: No such file or directory Aug 25 00:26:35 pop-os tracker-extract[22122]: Could not get mimetype, Error when getting information for file “/usr/share/applications/org.gnome.Nautilus.desktop.dpkg-tmp”: No such file or directory Aug 25 00:26:35 pop-os tracker-extract[22122]: Task for 'file:///usr/share/applications/org.gnome.Nautilus.desktop.dpkg-tmp' finished with error: Error when getting information for file “/usr/share/applications/org.gnome.Nautilus.desktop.dpkg-tmp”: No such file or directory Aug 25 00:33:04 pop-os kernel: nautilus[28293]: segfault at 58 ip 7f357c875052 sp 7ffeefa99f58 error 4 in libpython3.10.so.1.0[7f357c85f000+22d000] ``` The segfaults are when running `$ nautilus` and "Error when getting information for file..." when running `sudo apt install --reinstall nautilus` help very much appreciated :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1987572/+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
