[Desktop-packages] [Bug 2061214] [NEW] Software sources not correctly updated after upgrade
Public bug reported: Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 13 11:44:28 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240331) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00 ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: Software sources not correctly updated after upgrade Status in software-properties package in Ubuntu: New Bug description: Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 13 11:44:28 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240331) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+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 2050884] Re: Ubuntu Metrics server is not accepting reports
Confirm this no longer present in Ubuntu Noble Desktop daily ISO dated 20240410 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2050884 Title: Ubuntu Metrics server is not accepting reports Status in gnome-initial-setup package in Ubuntu: Fix Committed Status in ubuntu-report package in Ubuntu: Triaged Bug description: gnome-initial-setup now prompts to send a report immediately, and when it does, it fails, I'll attach a screenshot in the comments. Even when I clicked "Don't send to ubuntu" or however it's phrased, I still encountered the error message pop up in the comments. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-initial-setup 46~alpha-2ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 10:38:31 2024 InstallationDate: Installed on 2024-01-23 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2050884/+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 2052383] [NEW] gjs-console crashed with signal 5
Public bug reported: Testing Ubuntu Noble Desktop daily ISO dated 04-02-2024 This error occurred when running post-instalation tests re: link https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs opened and closed "foliate" app and the bug appeared. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gjs 1.78.3-1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Feb 4 14:28:38 2024 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2024-02-04 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240204) JournalErrors: Feb 04 14:28:38 username-Default-string foliate[7166]: Failed to fully launch dbus-proxy: Child process exited with code 1 ProcCmdline: /usr/bin/gjs-console -m /usr/bin/foliate ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 5 SourcePackage: gjs StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 Title: gjs-console crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash noble wayland-session ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2052383 Title: gjs-console crashed with signal 5 Status in gjs package in Ubuntu: New Bug description: Testing Ubuntu Noble Desktop daily ISO dated 04-02-2024 This error occurred when running post-instalation tests re: link https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs opened and closed "foliate" app and the bug appeared. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gjs 1.78.3-1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Feb 4 14:28:38 2024 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2024-02-04 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240204) JournalErrors: Feb 04 14:28:38 username-Default-string foliate[7166]: Failed to fully launch dbus-proxy: Child process exited with code 1 ProcCmdline: /usr/bin/gjs-console -m /usr/bin/foliate ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 5 SourcePackage: gjs StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 Title: gjs-console crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2052383/+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 2043915] Re: Booting into live session results in try/install page white screen
Tested Ubuntu Noble Desktop daily ISO dated 16-01-2024 and bug was not present Fix confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2049210] Re: After install Rasp Pi 4 - system fails to send report info to metrics server
** Summary changed: - After install system fails to send report info to metrics server + After install Rasp Pi 4 - system fails to send report info to metrics server -- 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/2049210 Title: After install Rasp Pi 4 - system fails to send report info to metrics server Status in xorg package in Ubuntu: New Bug description: Testing Rasp Pi Ubuntu Noble daily iso dated 12-01-2024 After install system fails to send report info to metrics server, (client:timeout exceeded while awaiting headers. Will also attach screenshot of error received. Not sure if this is correct package for the bug report - ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu6 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 14:26:42 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:D1:2B:AD vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd multipath=off dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.117-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.0-2ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 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/+bug/2049210/+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 2049210] Re: After install system fails to send report info to metrics server
Attached is screenshot of error ** Attachment added: "20240112_140420[1].jpg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2049210/+attachment/5738774/+files/20240112_140420%5B1%5D.jpg -- 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/2049210 Title: After install Rasp Pi 4 - system fails to send report info to metrics server Status in xorg package in Ubuntu: New Bug description: Testing Rasp Pi Ubuntu Noble daily iso dated 12-01-2024 After install system fails to send report info to metrics server, (client:timeout exceeded while awaiting headers. Will also attach screenshot of error received. Not sure if this is correct package for the bug report - ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu6 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 14:26:42 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:D1:2B:AD vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd multipath=off dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.117-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.0-2ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 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/+bug/2049210/+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 2049210] [NEW] After install Rasp Pi 4 - system fails to send report info to metrics server
Public bug reported: Testing Rasp Pi Ubuntu Noble daily iso dated 12-01-2024 After install system fails to send report info to metrics server, (client:timeout exceeded while awaiting headers. Will also attach screenshot of error received. Not sure if this is correct package for the bug report - ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu6 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 14:26:42 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:D1:2B:AD vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd multipath=off dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.117-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.0-2ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 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: apport-bug arm64 noble reproducible ubuntu wayland-session -- 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/2049210 Title: After install Rasp Pi 4 - system fails to send report info to metrics server Status in xorg package in Ubuntu: New Bug description: Testing Rasp Pi Ubuntu Noble daily iso dated 12-01-2024 After install system fails to send report info to metrics server, (client:timeout exceeded while awaiting headers. Will also attach screenshot of error received. Not sure if this is correct package for the bug report - ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu6 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 14:26:42 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:D1:2B:AD vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd multipath=off dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.117-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.0-2ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 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:
[Desktop-packages] [Bug 2042584] Re: Totem fails to play downloaded video
@vanvugt Daniel van Vugt @seb128 Sebastien Bacher Just for the record - yes - installed the codecs for gstreamer and all is well. Will file a bug re: the gstreamer codecs not being installed automatically - thanks for the info! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2042584 Title: Totem fails to play downloaded video Status in totem package in Ubuntu: Invalid Bug description: Testing Ubuntu Noble Desktop daily rasp pi4 image dated 02-11-2023 Totem fails to play downloaded video - attached are screenshots of the issue. This maybe duplicate of earlier bugs re:totem but as new release assume best to file new bug (older bugs are 1998782,1969512 and other duplicates ) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3 Uname: Linux 6.5.0-1006-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 2 16:44:35 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/2042584/+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 2042584] Re: Totem fails to play downloaded video
@vanvugt Daniel Understood and agree - but regarding the testcase is it then not a bug that the gstreamer codecs are not installed automatically and should a bug report be filed for that matter? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2042584 Title: Totem fails to play downloaded video Status in totem package in Ubuntu: Invalid Bug description: Testing Ubuntu Noble Desktop daily rasp pi4 image dated 02-11-2023 Totem fails to play downloaded video - attached are screenshots of the issue. This maybe duplicate of earlier bugs re:totem but as new release assume best to file new bug (older bugs are 1998782,1969512 and other duplicates ) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3 Uname: Linux 6.5.0-1006-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 2 16:44:35 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/2042584/+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 2042584] [NEW] Totem fails to play downloaded video
Public bug reported: Testing Ubuntu Noble Desktop daily rasp pi4 image dated 02-11-2023 Totem fails to play downloaded video - attached are screenshots of the issue. This maybe duplicate of earlier bugs re:totem but as new release assume best to file new bug (older bugs are 1998782,1969512 and other duplicates ) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3 Uname: Linux 6.5.0-1006-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 2 16:44:35 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 mantic wayland-session ** Attachment added: "Screenshot from 2023-11-02 16-44-12.png" https://bugs.launchpad.net/bugs/2042584/+attachment/5715361/+files/Screenshot%20from%202023-11-02%2016-44-12.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2042584 Title: Totem fails to play downloaded video Status in totem package in Ubuntu: New Bug description: Testing Ubuntu Noble Desktop daily rasp pi4 image dated 02-11-2023 Totem fails to play downloaded video - attached are screenshots of the issue. This maybe duplicate of earlier bugs re:totem but as new release assume best to file new bug (older bugs are 1998782,1969512 and other duplicates ) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3 Uname: Linux 6.5.0-1006-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 2 16:44:35 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/2042584/+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 2042584] Re: Totem fails to play downloaded video
and screenshot # 2 ** Attachment added: "Screenshot from 2023-11-02 16-43-22.png" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/2042584/+attachment/5715367/+files/Screenshot%20from%202023-11-02%2016-43-22.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2042584 Title: Totem fails to play downloaded video Status in totem package in Ubuntu: New Bug description: Testing Ubuntu Noble Desktop daily rasp pi4 image dated 02-11-2023 Totem fails to play downloaded video - attached are screenshots of the issue. This maybe duplicate of earlier bugs re:totem but as new release assume best to file new bug (older bugs are 1998782,1969512 and other duplicates ) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3 Uname: Linux 6.5.0-1006-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 2 16:44:35 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/2042584/+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 2034928] [NEW] gnome-shell crashed with signal 5 in g_log_structured_array()
Public bug reported: gnome-shell crashed with signal 5 in g_log_structured_array() Testing Ubuntu Mantic Desktop Daily ISO dated 08.09.2023 Booted the ISO media and the system crashed with an internal error ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 13:18:38 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash mantic need-amd64-retrace ** Information type changed from Private to Public -- 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/2034928 Title: gnome-shell crashed with signal 5 in g_log_structured_array() Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell crashed with signal 5 in g_log_structured_array() Testing Ubuntu Mantic Desktop Daily ISO dated 08.09.2023 Booted the ISO media and the system crashed with an internal error ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 13:18:38 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034928/+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 1998782] Re: Totem unable to play video on Raspberry Pi: "could not initialize OpenGL support"
Update : This bug is still present in Ubuntu Daily Mantic RaspPI ISO dated 01-09-2023 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1998782 Title: Totem unable to play video on Raspberry Pi: "could not initialize OpenGL support" Status in totem package in Ubuntu: Confirmed Bug description: Testing Ubuntu Lunar Daily RaspPI 4 image dated 2022-12-05 I received this error trying to play the video "big_buck_bunny" in Totem as per the testcase: This maybe a duplicate of the old bug 1969512 but as the error message is not the same a new bug is filed. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1004.10-raspi 5.19.7 Uname: Linux 5.19.0-1004-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 5 11:24:38 2022 ImageMediaBuild: 20221205 LogAlsaMixer: Simple mixer control 'PCM',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -1988 [78%] [-19.88dB] [on] SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1998782/+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 2028434] [NEW] gnome-control-center crashed with SIGSEGV in gtk_picture_set_filename()
*** This bug is a duplicate of bug 2015142 *** https://bugs.launchpad.net/bugs/2015142 Public bug reported: Testing Ubuntu Mantic Desktop daily ISO dated 22-07-2023 Attempted to change "Appearance Style" from Light to Dark resulted in the error message - gnome-control-center crashed with SIGSEGV in gtk_picture_set_filename() ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.3-1ubuntu3 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 22 15:14:22 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-07-22 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230722) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/gnome-control-center ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7fb068daa9dd :mov (%rbx),%rax PC (0x7fb068daa9dd) ok source "(%rbx)" (0x62632d782f6e6f69) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: gtk_picture_set_filename () from /lib/x86_64-linux-gnu/libgtk-4.so.1 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in gtk_picture_set_filename() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash mantic wayland-session ** Information type changed from Private to Public ** Description changed: Testing Ubuntu Mantic Desktop daily ISO dated 22-07-2023 - Attempted to change theme from Light to Dark resulted in the error - message - gnome-control-center crashed with SIGSEGV in + Attempted to change "Appearance Style" from Light to Dark resulted in + the error message - gnome-control-center crashed with SIGSEGV in gtk_picture_set_filename() ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.3-1ubuntu3 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 22 15:14:22 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-07-22 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230722) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/gnome-control-center ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= SegvAnalysis: - Segfault happened at: 0x7fb068daa9dd : mov (%rbx),%rax - PC (0x7fb068daa9dd) ok - source "(%rbx)" (0x62632d782f6e6f69) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x7fb068daa9dd : mov (%rbx),%rax + PC (0x7fb068daa9dd) ok + source "(%rbx)" (0x62632d782f6e6f69) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: - gtk_picture_set_filename () from /lib/x86_64-linux-gnu/libgtk-4.so.1 - g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 - ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + gtk_picture_set_filename () from /lib/x86_64-linux-gnu/libgtk-4.so.1 + g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in gtk_picture_set_filename() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: -- 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/2028434 Title: gnome-control-center crashed with SIGSEGV in gtk_picture_set_filename() Status in gnome-control-center package in Ubuntu: New Bug description:
[Desktop-packages] [Bug 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic
Tested ASRock H410M-HDV i5-10400 Motherboard,32GB,Intel UHD Graphics 630,Ethernet,Intel 660p 512GB M.2 NVMe SSD - Lubuntu Jammy daily ISO 13-05-2023 Testing apport proposed fix 2.20.11-0ubuntu82.5 re bug 1973470 - confirm the bug is no longer present ** Tags removed: verification-needed ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1973470 Title: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in xdg-utils package in Ubuntu: Invalid Status in apport source package in Jammy: Fix Committed Status in xdg-utils source package in Jammy: New Bug description: Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD. While reporting Bug #1973469, I discovered that ubuntu-bug was unable to open Firefox at the very end of the process. Sadly, I closed the terminal window that contained the initial error, but I was able to easily reproduce it reporting this bug. The full console output of "ubuntu-bug apport" on Lubuntu Kinetic is: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 94% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?' I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this is due to the Snap version of Firefox, but I don't know for sure. Since ubuntu-bug is what gave me the error, I'm filing this against Apport. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: LXQt Date: Sun May 15 11:41:07 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1973470/+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 1998782] Re: Totem unable to play video on Raspberry Pi: "could not initialize OpenGL support"
This bug is still present in Ubuntu Daily Mantic RaspPI ISO dated 12-05-2023 ** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1998782 Title: Totem unable to play video on Raspberry Pi: "could not initialize OpenGL support" Status in totem package in Ubuntu: Confirmed Bug description: Testing Ubuntu Lunar Daily RaspPI 4 image dated 2022-12-05 I received this error trying to play the video "big_buck_bunny" in Totem as per the testcase: This maybe a duplicate of the old bug 1969512 but as the error message is not the same a new bug is filed. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1004.10-raspi 5.19.7 Uname: Linux 5.19.0-1004-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 5 11:24:38 2022 ImageMediaBuild: 20221205 LogAlsaMixer: Simple mixer control 'PCM',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -1988 [78%] [-19.88dB] [on] SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1998782/+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 1969512] Re: Totem unable to play video: "The specified movie could not be found"
Received this error testing Ubuntu Jammy image dated 2023-02-17.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Fix Released Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+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 1999298] [NEW] gnome-initial-setup crashes when attempting install Ubuntu Lunar
Public bug reported: Testing Ubuntu Lunar daily ISO dated 2022-12-20 When attempting to install Lubuntu Lunar the "Install or Try Ubuntu icons never appear on desktop after boot. The desktop appears after booting but is empty (shows only background wallpaper) See attached screenshot. Test 2 machines 1. Dell Optiplex 7060 running in UEFI + secure boot mode.and 2. Dell Optiplex 704 running in UEFI mode. Will attach syslog and casper log files Test results here: http://iso.qa.ubuntu.com/qatracker/milestones/441/builds/265663/testcases/1300/results ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Tags: lunar ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1999298/+attachment/5635287/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1999298 Title: gnome-initial-setup crashes when attempting install Ubuntu Lunar Status in gnome-initial-setup package in Ubuntu: New Bug description: Testing Ubuntu Lunar daily ISO dated 2022-12-20 When attempting to install Lubuntu Lunar the "Install or Try Ubuntu icons never appear on desktop after boot. The desktop appears after booting but is empty (shows only background wallpaper) See attached screenshot. Test 2 machines 1. Dell Optiplex 7060 running in UEFI + secure boot mode.and 2. Dell Optiplex 704 running in UEFI mode. Will attach syslog and casper log files Test results here: http://iso.qa.ubuntu.com/qatracker/milestones/441/builds/265663/testcases/1300/results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1999298/+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 1998782] [NEW] Totem unable to play video : "could not initialize OpenGL support"
Public bug reported: Testing Ubuntu Lunar Daily RaspPI 4 image dated 2022-12-05 I received this error trying to play the video "big_buck_bunny" in Totem as per the testcase: This maybe a duplicate of the old bug 1969512 but as the error message is not the same a new bug is filed. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1004.10-raspi 5.19.7 Uname: Linux 5.19.0-1004-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 5 11:24:38 2022 ImageMediaBuild: 20221205 LogAlsaMixer: Simple mixer control 'PCM',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -1988 [78%] [-19.88dB] [on] SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image lunar raspi-image wayland-session ** Attachment added: "Screenshot from 2022-12-05 11-23-50.png" https://bugs.launchpad.net/bugs/1998782/+attachment/5634551/+files/Screenshot%20from%202022-12-05%2011-23-50.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1998782 Title: Totem unable to play video : "could not initialize OpenGL support" Status in totem package in Ubuntu: New Bug description: Testing Ubuntu Lunar Daily RaspPI 4 image dated 2022-12-05 I received this error trying to play the video "big_buck_bunny" in Totem as per the testcase: This maybe a duplicate of the old bug 1969512 but as the error message is not the same a new bug is filed. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1004.10-raspi 5.19.7 Uname: Linux 5.19.0-1004-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 5 11:24:38 2022 ImageMediaBuild: 20221205 LogAlsaMixer: Simple mixer control 'PCM',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -1988 [78%] [-19.88dB] [on] SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1998782/+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 1982935] [NEW] Selecting "restore defaults" in software-properties-qt has no effect
Public bug reported: Testing Lubuntu Kinetic daily ISO 26-07-2022 1. Open "Software Sources" from "Preferences menu 2. Select "Authentication" 3. Delete the keys from "Trusted Service Providers" 4. Select "Restore Defaults" 5. After selecting "Restore Defaults" - nothing happens i.e the keys are not restored resulting in the user being unable to perform updates to the system. This bug is most likely related to bug 11795278 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278 Attached is a screenshot after removing the keys re: step #3 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: software-properties-qt 0.99.25 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Wed Jul 27 09:19:33 2022 InstallationDate: Installed on 2022-07-27 (0 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ** Attachment added: "screen4.jpg" https://bugs.launchpad.net/bugs/1982935/+attachment/5605558/+files/screen4.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1982935 Title: Selecting "restore defaults" in software-properties-qt has no effect Status in software-properties package in Ubuntu: New Bug description: Testing Lubuntu Kinetic daily ISO 26-07-2022 1. Open "Software Sources" from "Preferences menu 2. Select "Authentication" 3. Delete the keys from "Trusted Service Providers" 4. Select "Restore Defaults" 5. After selecting "Restore Defaults" - nothing happens i.e the keys are not restored resulting in the user being unable to perform updates to the system. This bug is most likely related to bug 11795278 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278 Attached is a screenshot after removing the keys re: step #3 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: software-properties-qt 0.99.25 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Wed Jul 27 09:19:33 2022 InstallationDate: Installed on 2022-07-27 (0 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1982935/+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 1972009] [NEW] Totem fails to find video - kinetic ubuntu raspi pi
Public bug reported: Running test kinetic ubuntu daily - raspi 4 8GB daily ISO When attempting to run "totem big_buck_bunny_720p_surround.mp4" as per the testcase - received the error - An error occurred - the specified movie could not be found. No further errors encountered -- I ran ubuntu-bug totem but see that the package selected is "gstreamer1.0" - please correct if need be. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-1006.6-raspi 5.15.30 Uname: Linux 5.15.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 6 17:07:53 2022 ImageMediaBuild: 20220506 LogAlsaMixer: Simple mixer control 'Headphone',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -2000 [77%] [-20.00dB] [on] SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image kinetic raspi-image wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972009 Title: Totem fails to find video - kinetic ubuntu raspi pi Status in gstreamer1.0 package in Ubuntu: New Bug description: Running test kinetic ubuntu daily - raspi 4 8GB daily ISO When attempting to run "totem big_buck_bunny_720p_surround.mp4" as per the testcase - received the error - An error occurred - the specified movie could not be found. No further errors encountered -- I ran ubuntu-bug totem but see that the package selected is "gstreamer1.0" - please correct if need be. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-1006.6-raspi 5.15.30 Uname: Linux 5.15.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 6 17:07:53 2022 ImageMediaBuild: 20220506 LogAlsaMixer: Simple mixer control 'Headphone',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -2000 [77%] [-20.00dB] [on] SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972009/+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 1966589] Re: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1`
@brian-murray No I did not install the Firefox snap prior to upgrade. Just performed normal upgrades. All Lubuntu Jammy upgrades I performed since 04-04-2022 from Focal and Impish upgraded with no errors and no problem with the Firefox snap. The last upgrades test results here : http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/246675/testcases It looks to me that this issue is fixed. -- 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/1966589 Title: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1` Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1966589] Re: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1`
Tested Dell [ Optiplex] MT 7040, and also Dell [ Optiplex] MT 7040,upgrading from Lubuntu Focal 20.04,4 to Lubuntu Jammy tests dated 04-04-2022 - upgrades performed with no errors. http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/246405/testcases/1635/results/ -- 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/1966589 Title: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1` Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] Re: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1`
@brian-murray Brian Tested Dell Latitude 7280 box 03.04.2022 Before running the upgrade Lubuntu Focal to Lubuntu Jammy I installed Firefox snap with command "snap install firefox" rebooted and ran the "sudo do-release-upgrade -d". The system upgraded and without errors. -- 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/1966589 Title: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1` Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] Re: Upgrader unable to contact snap store
Tested again - this time with TUI interface (do-release-upgrade) from a terminal and the upgrade finished with the error - "This upgrade has finished but there were errors.." During the upgrade I noticed that the snap store was not contacted. After reboot I noticed that Firefox was still the deb version - opened Discover to apply updates and noticed (see screenshot) that758.4 MB were waiting to update. Comments 6 to 14 are from this upgrade. Also note - running lsb_release - r shows 22.04 (wallpaper not updated) and Prompt shows = Prompt=lts I thought best to not file a new bug report as it seems to be same result of snap store. ** Attachment added: "screen1.jpg" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1966589/+attachment/5574769/+files/screen1.jpg -- 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/1966589 Title: Upgrader unable to contact snap store Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9
[Desktop-packages] [Bug 1966589] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1966589/+attachment/5574768/+files/PulseList.txt -- 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/1966589 Title: Upgrader unable to contact snap store Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1966589/+attachment/5574764/+files/PciNetwork.txt -- 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/1966589 Title: Upgrader unable to contact snap store Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1966589/+attachment/5574765/+files/ProcCpuinfoMinimal.txt -- 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/1966589 Title: Upgrader unable to contact snap store Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1966589/+attachment/5574766/+files/ProcEnviron.txt -- 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/1966589 Title: Upgrader unable to contact snap store Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] Profile0Prefs.txt
apport information ** Attachment added: "Profile0Prefs.txt" https://bugs.launchpad.net/bugs/1966589/+attachment/5574767/+files/Profile0Prefs.txt -- 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/1966589 Title: Upgrader unable to contact snap store Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1966589/+attachment/5574763/+files/Lspci.txt -- 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/1966589 Title: Upgrader unable to contact snap store Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1966589/+attachment/5574761/+files/Dependencies.txt -- 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/1966589 Title: Upgrader unable to contact snap store Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1966589/+attachment/5574762/+files/IpAddr.txt -- 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/1966589 Title: Upgrader unable to contact snap store Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1966589/+attachment/5574760/+files/CurrentDmesg.txt -- 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/1966589 Title: Upgrader unable to contact snap store Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] Re: Upgrader unable to contact snap store
apport information ** Tags added: apport-collected ** Description changed: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting + --- + ProblemType: Bug + AddonCompatCheckDisabled: False + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: kf 950 F pulseaudio + BuildID: 20220322144853 + CasperMD5CheckResult: skip + Channel: Unavailable + CurrentDesktop: LXQt + DefaultProfileExtensions: extensions.sqlite corrupt or missing + DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) + DefaultProfileLocales: extensions.sqlite corrupt or missing + DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 + DefaultProfileThemes: extensions.sqlite corrupt or missing + DistroRelease: Ubuntu 22.04 + ForcedLayersAccel: False + InstallationDate: Installed on 2022-03-30 (0 days ago) + InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) + IpRoute: + default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 + 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 + Package: ubuntu-release-upgrader + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 + Profile0Extensions: extensions.sqlite corrupt or missing + Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) + Profile0Locales: extensions.sqlite corrupt or missing + Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 + Profile0PrefSources: prefs.js + Profile0Themes: extensions.sqlite corrupt or missing + Profiles: + Profile1 (Default) - LastVersion=None/None (Out of date) + Profile0 - LastVersion=98.0.2/20220322144853 (In use) + RunningIncompatibleAddons: False + Tags: jammy + Uname: Linux 5.13.0-39-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sudo + _MarkForUpload: True + dmi.bios.date: 07/08/2021 + dmi.bios.release: 1.20 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.20.2 + dmi.board.name: 0Y7WYT + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 3 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: + dmi.product.family: OptiPlex + dmi.product.name: OptiPlex 7040 + dmi.product.sku: 06B9 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1966589/+attachment/5574759/+files/AlsaInfo.txt -- 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/1966589 Title: Upgrader unable to contact snap store Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed.
[Desktop-packages] [Bug 1964579] Re: Pulseaudio fails to detect /enable Intel SST sound card
This error also affecting Lubuntu,Ubuntu Budgie and Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1964579 Title: Pulseaudio fails to detect /enable Intel SST sound card Status in pulseaudio package in Ubuntu: New Bug description: Testing Live session and also full install Ubuntu Mate Jammy daily ISO 11-03-2022 The machine tested - AEROFARA Aero2 Pro, N5105,8GB,Ethernet GB,WiFi,Bluetooth 4.0,128GB SSD,Intel UHD Graphics The audio card is not detected - entering sound preferences settings - "output" only shows dummy output stereo - under "hardware" is no entry available ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CasperVersion: 1.467 CurrentDesktop: MATE Date: Fri Mar 11 09:25:31 2022 LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220311) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Digital Out, HDMI Title: [AERO 2 Pro, Intel Jasperlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: JB1006 dmi.board.asset.tag: Default string dmi.board.name: AERO 2 Pro dmi.board.vendor: Shenzhen Wangang Technology Co., Ltd dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB1006:bd12/13/2021:br5.19:efr0.7:svnShenzhenWangangTechnologyCo.,Ltd:pnAERO2Pro:pvrDefaultstring:rvnShenzhenWangangTechnologyCo.,Ltd:rnAERO2Pro:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:skuAERO2Pro: dmi.product.family: Windows 10 Pro dmi.product.name: AERO 2 Pro dmi.product.sku: AERO 2 Pro dmi.product.version: Default string dmi.sys.vendor: Shenzhen Wangang Technology Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1964579/+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 1964579] Re: Pulseaudio fails to detect card
** Summary changed: - [AERO 2 Pro, Intel Jasperlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card + Pulseaudio fails to detect card ** Summary changed: - Pulseaudio fails to detect card + Pulseaudio fails to detect /enable card ** Summary changed: - Pulseaudio fails to detect /enable card + Pulseaudio fails to detect /enable Intel SST sound card -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1964579 Title: Pulseaudio fails to detect /enable Intel SST sound card Status in pulseaudio package in Ubuntu: New Bug description: Testing Live session and also full install Ubuntu Mate Jammy daily ISO 11-03-2022 The machine tested - AEROFARA Aero2 Pro, N5105,8GB,Ethernet GB,WiFi,Bluetooth 4.0,128GB SSD,Intel UHD Graphics The audio card is not detected - entering sound preferences settings - "output" only shows dummy output stereo - under "hardware" is no entry available ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CasperVersion: 1.467 CurrentDesktop: MATE Date: Fri Mar 11 09:25:31 2022 LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220311) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Digital Out, HDMI Title: [AERO 2 Pro, Intel Jasperlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: JB1006 dmi.board.asset.tag: Default string dmi.board.name: AERO 2 Pro dmi.board.vendor: Shenzhen Wangang Technology Co., Ltd dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB1006:bd12/13/2021:br5.19:efr0.7:svnShenzhenWangangTechnologyCo.,Ltd:pnAERO2Pro:pvrDefaultstring:rvnShenzhenWangangTechnologyCo.,Ltd:rnAERO2Pro:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:skuAERO2Pro: dmi.product.family: Windows 10 Pro dmi.product.name: AERO 2 Pro dmi.product.sku: AERO 2 Pro dmi.product.version: Default string dmi.sys.vendor: Shenzhen Wangang Technology Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1964579/+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 1964579] Re: [AERO 2 Pro, Intel Jasperlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card
Looking at the alsainfo.txt - I can see that the card is detected but not enabled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1964579 Title: Pulseaudio fails to detect /enable card Status in pulseaudio package in Ubuntu: New Bug description: Testing Live session and also full install Ubuntu Mate Jammy daily ISO 11-03-2022 The machine tested - AEROFARA Aero2 Pro, N5105,8GB,Ethernet GB,WiFi,Bluetooth 4.0,128GB SSD,Intel UHD Graphics The audio card is not detected - entering sound preferences settings - "output" only shows dummy output stereo - under "hardware" is no entry available ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CasperVersion: 1.467 CurrentDesktop: MATE Date: Fri Mar 11 09:25:31 2022 LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220311) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Digital Out, HDMI Title: [AERO 2 Pro, Intel Jasperlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: JB1006 dmi.board.asset.tag: Default string dmi.board.name: AERO 2 Pro dmi.board.vendor: Shenzhen Wangang Technology Co., Ltd dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB1006:bd12/13/2021:br5.19:efr0.7:svnShenzhenWangangTechnologyCo.,Ltd:pnAERO2Pro:pvrDefaultstring:rvnShenzhenWangangTechnologyCo.,Ltd:rnAERO2Pro:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:skuAERO2Pro: dmi.product.family: Windows 10 Pro dmi.product.name: AERO 2 Pro dmi.product.sku: AERO 2 Pro dmi.product.version: Default string dmi.sys.vendor: Shenzhen Wangang Technology Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1964579/+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 1964579] [NEW] Pulseaudio fails to detect /enable card
Public bug reported: Testing Live session and also full install Ubuntu Mate Jammy daily ISO 11-03-2022 The machine tested - AEROFARA Aero2 Pro, N5105,8GB,Ethernet GB,WiFi,Bluetooth 4.0,128GB SSD,Intel UHD Graphics The audio card is not detected - entering sound preferences settings - "output" only shows dummy output stereo - under "hardware" is no entry available ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CasperVersion: 1.467 CurrentDesktop: MATE Date: Fri Mar 11 09:25:31 2022 LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220311) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Digital Out, HDMI Title: [AERO 2 Pro, Intel Jasperlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: JB1006 dmi.board.asset.tag: Default string dmi.board.name: AERO 2 Pro dmi.board.vendor: Shenzhen Wangang Technology Co., Ltd dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB1006:bd12/13/2021:br5.19:efr0.7:svnShenzhenWangangTechnologyCo.,Ltd:pnAERO2Pro:pvrDefaultstring:rvnShenzhenWangangTechnologyCo.,Ltd:rnAERO2Pro:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:skuAERO2Pro: dmi.product.family: Windows 10 Pro dmi.product.name: AERO 2 Pro dmi.product.sku: AERO 2 Pro dmi.product.version: Default string dmi.sys.vendor: Shenzhen Wangang Technology Co., Ltd ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: - Testing Live session Ubuntu Mate Jammy daily ISO 11-03-2022 + Testing Live session and also full install Ubuntu Mate Jammy daily ISO + 11-03-2022 + + The machine tested - AEROFARA Aero2 Pro, N5105,8GB,Ethernet + GB,WiFi,Bluetooth 4.0,128GB SSD,Intel UHD Graphics The audio card is not detected - entering sound preferences settings - "output" only shows dummy output stereo - under "hardware" is no entry available ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CasperVersion: 1.467 CurrentDesktop: MATE Date: Fri Mar 11 09:25:31 2022 LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220311) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Digital Out, HDMI Title: [AERO 2 Pro, Intel Jasperlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: JB1006 dmi.board.asset.tag: Default string dmi.board.name: AERO 2 Pro dmi.board.vendor: Shenzhen Wangang Technology Co., Ltd dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB1006:bd12/13/2021:br5.19:efr0.7:svnShenzhenWangangTechnologyCo.,Ltd:pnAERO2Pro:pvrDefaultstring:rvnShenzhenWangangTechnologyCo.,Ltd:rnAERO2Pro:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:skuAERO2Pro: dmi.product.family: Windows 10 Pro
[Desktop-packages] [Bug 1963770] Re: gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1964458 ***
https://bugs.launchpad.net/bugs/1964458
** This bug has been marked a duplicate of bug 1964463
Ubuntu Jammy gnome-shell crashed with SIGSEGV
--
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/1963770
Title:
gnome-shell crashed with SIGSEGV
Status in gnome-shell package in Ubuntu:
Invalid
Bug description:
Twice seen after starting the Firefox snap in a live session.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 5 22:30:08 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220305)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
PATH=(custom, no user)
LANG=C.UTF-8
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 41.3-3ubuntu1
SegvAnalysis:
Segfault happened at: 0x7f1cb6d891b4:mov(%rsi),%rax
PC (0x7f1cb6d891b4) ok
source "(%rsi)" (0x1c402550) not located in a known VMA region (needed
readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
#0 0x7f1cb6d891b4 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffc18248c90
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963770/+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 1964463] [NEW] Ubuntu Jammy gnome-shell crashed with SIGSEGV
Public bug reported:
Testing Ubuntu Jammy Live session daily iso 10-03-2022
gnome-shell crashed after selecting Firefox snap
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.467
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 10 10:13:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 'au'),
('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
PATH=(custom, no user)
LANG=C.UTF-8
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 41.3-3ubuntu1
SegvAnalysis:
Segfault happened at: 0x7f04cd0f7f44: mov(%rsi),%rax
PC (0x7f04cd0f7f44) ok
source "(%rsi)" (0x2d78d420) not located in a known VMA region (needed
readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
#0 0x7f04cd0f7f44 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7fff167a9950
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-crash jammy
** Information type changed from Private to Public
--
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/1964463
Title:
Ubuntu Jammy gnome-shell crashed with SIGSEGV
Status in gnome-shell package in Ubuntu:
Confirmed
Bug description:
Testing Ubuntu Jammy Live session daily iso 10-03-2022
gnome-shell crashed after selecting Firefox snap
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.467
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 10 10:13:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
PATH=(custom, no user)
LANG=C.UTF-8
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 41.3-3ubuntu1
SegvAnalysis:
Segfault happened at: 0x7f04cd0f7f44:mov(%rsi),%rax
PC (0x7f04cd0f7f44) ok
source "(%rsi)" (0x2d78d420) not located in a known VMA region (needed
readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
#0 0x7f04cd0f7f44 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7fff167a9950
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964463/+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 1963770] Re: gnome-shell crashed with SIGSEGV
I can confirm this bug also occurred while testing Ubuntu Jammy QA ISO
05-03-2022
--
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/1963770
Title:
gnome-shell crashed with SIGSEGV
Status in gnome-shell package in Ubuntu:
Confirmed
Bug description:
Twice seen after starting the Firefox snap in a live session.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 5 22:30:08 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220305)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
PATH=(custom, no user)
LANG=C.UTF-8
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 41.3-3ubuntu1
SegvAnalysis:
Segfault happened at: 0x7f1cb6d891b4:mov(%rsi),%rax
PC (0x7f1cb6d891b4) ok
source "(%rsi)" (0x1c402550) not located in a known VMA region (needed
readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
#0 0x7f1cb6d891b4 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffc18248c90
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963770/+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 1960226] Re: Ubuntu Jammy Desktop fails to boot after install
2022-02-09 Fails Ran 2 tests - http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/244128/testcases/1300/results -- 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/1960226 Title: Ubuntu Jammy Desktop fails to boot after install Status in systemd package in Ubuntu: Incomplete Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Jammy Desktop fails to boot after install Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07 This also affects Ubuntu Jammy Canary desktop - tested daily ISO 2022-02-07 After installing the OS and selecting reboot the system reboot fails - The vendors logo appears with the Ubuntu logo and fails to boot - I have tried this with 2 barebone machines and 1 in VirtualBox - will attach syslogs and images in a separate comment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960226/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Hello Brian (brian-murray) Please see my comment #9 above - i have run numerous tests on Xubuntu Impish and have been unable to reproduce this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Impish: Fix Committed Bug description: * Impact The pulseaudio service sometime segfaults on session closing which trigger a bug report dialog * Test plan Log out of a desktop session and back in, there should be no error prompt The issue isn't triggered only randomly it seems so it might be easier to check that reports stop on https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e * Where problems could occur The change is in the X session closing handling so shouldn't impact on normal use, if incorrect the fix could lead to increase the chance of hitting the segfault when an Xsession is closed --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1942685/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
@brian-murray - Yes I will continue to test but fyi - I have run 24 tests on Xubuntu (18 different ISO´s) since the original report without being able to reproduce the error. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942685/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Tested Xubuntu Impish daily 29-09-2021 and was unable to to reproduce the bug - This test was on the same machine (Lenovo V14-IIL) as my initial report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942685/+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 1942685] [NEW] pulseaudio crashed with SIGSEGV in _IceTransClose()
Public bug reported: Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash impish ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in pulseaudio package in Ubuntu: New Bug description: Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to:
[Desktop-packages] [Bug 1936893] Re: Gnome-software says internet access not available while i'm connected
Confirmimg comment #9 @glx Testing Ubuntu Impish daily ISO 28-08-2021 Also receiving this error while attempting to install software - The error is: "Unable to install: Internet access required but wasn't available' I then entered `sudo systemctl restart packagekit` and then was able to install software. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1936893 Title: Gnome-software says internet access not available while i'm connected Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: Started gnome-software, click on 'Updates' gnome-software says: 'Unable to download updates: Internet access required but wasn't available' while I'm connected via wifi. see nmcli output and attached screenshot. corrado@corrado-n4-ii-0718:~$ nmcli connection show NAMEUUID TYPE DEVICE corado 62241493-d859-4bcd-9843-7f158233130b wifi wlp2s0 Wired connection 1 72d727fa-2f49-3b54-a39f-2a059e6948c7 ethernet -- corrado@corrado-n4-ii-0718:~$ nmcli -f connection.metered connection show 62241493-d859-4bcd-9843-7f158233130b connection.metered: unknown corrado@corrado-n4-ii-0718:~$ busctl get-property org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager Metered u 3 corrado@corrado-n4-ii-0718:~$ The problem was different: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/996 before today updates: Start-Date: 2021-07-20 06:35:15 Commandline: apt upgrade Requested-By: corrado (1000) Install: gir1.2-clutter-gst-3.0:amd64 (3.0.27-2, automatic), gir1.2-gtkclutter-1.0:amd64 (1.8.4-4, automatic) Upgrade: ubuntu-drivers-common:amd64 (1:0.8.9.1, 1:0.9.1.2), gnome-shell-extension-desktop-icons-ng:amd64 (0.18.0-0ubuntu2, 0.18.0-0ubuntu3), netplan.io:amd64 (0.102-0ubuntu4, 0.102-0ubuntu6), libnetplan0:amd64 (0.102-0ubuntu4, 0.102-0ubuntu6), libnspr4:amd64 (2:4.29-1, 2:4.32-1) End-Date: 2021-07-20 06:35:20 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-software 3.38.1-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 20 07:36:06 2021 InstallationDate: Installed on 2021-07-18 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210718) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.1-1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-07-18 (8 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210718) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.1-1 Package: gnome-software 3.38.1-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Tags: wayland-session impish Uname: Linux 5.11.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1936893/+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 1936826] Re: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
** Description changed:
Testing daily Ubuntu Impish ISO 2021-07-19
+
+ Test machine : Dell [Latitude] 7280 (i5-7300U,
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings" app
and selected "Appearance".
-
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
Status in gnome-shell package in Ubuntu:
New
Bug description:
Testing daily Ubuntu Impish ISO 2021-07-19
Test machine : Dell [Latitude] 7280 (i5-7300U,
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings"
app and selected "Appearance".
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1936826/+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 1936826] Re: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
** Information type changed from Private to Public
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
Status in gnome-shell package in Ubuntu:
New
Bug description:
Testing daily Ubuntu Impish ISO 2021-07-19
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings"
app and selected "Appearance".
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1936826/+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 1936643] Re: Logging in to GNOME 40.2.0 causes desktop icon extension to show as application in Activities overview
Another quick confirm - tested on ISO 210719 Ubuntu Impish from the Qa testing site. Tested in VirtualBox and on bare metal. Otherwise all looked good. -- 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/1936643 Title: Logging in to GNOME 40.2.0 causes desktop icon extension to show as application in Activities overview Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: In Ubuntu 21.10 Impish Indri, I have done today's updates, including GNOME 40, and when I rebooted, I saw the desktop icons in the Activities overview that has the grey gears icon and the gibberish name. However, when I clicked on it, I'm taken to the desktop. When I open the Activities overview again, that "application" didn't show up. I suspect that this "application" came from a GNOME extension that handles desktop icons, called gnome-shell-extension-desktop-icons-ng. Because I thought that it loaded AFTER the Activities overview opened at log in. This repeats every time I reboot or just log off and log back in. Steps to reproduce: 1. Update the Impish system to the latest version 2. Reboot 3. Log in Expected results: The "application" that came from the desktop icon shell extension doesn't appear in the Activities overview Actual results: This "application" shows up in the overview with the grey gears icon and the gibberish name every time a user signs in to the new GNOME 40 desktop lsb_release -rd: Description: Ubuntu Impish Indri (development branch) Release: 21.10 apt-cache policy gnome-shell: gnome-shell: Installed: 40.2-1ubuntu1 Candidate: 40.2-1ubuntu1 Version table: *** 40.2-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status If there is any more information needed, let me know. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 16 15:07:53 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-02-02 (163 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1936643/+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 1930447] [NEW] Unable to turn on bluetooth
Public bug reported: Testing Ubuntu Impish daily ISO 01-06-2021 0n QA tracking site - After successful install go to settings "Bluetooth" and select the on tab in upper right hand corner and nothing happens. This maybe related to bug # 1928924 https://bugs.launchpad.net/ubuntu/+source/bluedevil/+bug/1928924 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.58-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 16:30:07 2021 InstallationDate: Installed on 2021-06-01 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210601) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 82C4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=efd131f1-9709-400b-9f5d-d72be1df3885 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 28:39:26:D5:7D:8E ACL MTU: 1021:6 SCO MTU: 255:12 DOWN RX bytes:1682 acl:0 sco:0 events:183 errors:0 TX bytes:36490 acl:0 sco:0 commands:183 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1930447 Title: Unable to turn on bluetooth Status in bluez package in Ubuntu: New Bug description: Testing Ubuntu Impish daily ISO 01-06-2021 0n QA tracking site - After successful install go to settings "Bluetooth" and select the on tab in upper right hand corner and nothing happens. This maybe related to bug # 1928924 https://bugs.launchpad.net/ubuntu/+source/bluedevil/+bug/1928924 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.58-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 16:30:07 2021 InstallationDate: Installed on 2021-06-01 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210601) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 82C4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=efd131f1-9709-400b-9f5d-d72be1df3885 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 28:39:26:D5:7D:8E ACL MTU: 1021:6 SCO MTU: 255:12 DOWN RX bytes:1682 acl:0 sco:0 events:183 errors:0 TX bytes:36490 acl:0 sco:0 commands:183 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1930447/+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 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I can confirm the fix works. Tested daily ISO Kubuntu Hirsute ISO 20210409 with VirtualBox and no errors. See results here: http://iso.qa.ubuntu.com/qatracker/milestones/419/builds/229247/testcases/1300/results -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Fix Released Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
@rikmills Tested your suggestion in comment #35 and installed with no errors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
@rikmills Crash in VirtualBox but real hardware (Lenovo 450) no crash ISO 2021-03-23 same as yr comment #6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in mesa source package in Hirsute: New Status in ubiquity source package in Hirsute: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1919313] [NEW] Login screen has Ubuntu and not Budgiedesktop as default
Public bug reported: This occurred after installing Ubuntu Budgie Hirsute (21.04) from the daily ISO 20210315.1 The gdm package is 3.38.21-2 ubuntu 1 After installing the system and rebooting when the login screen appears the default desktop is Ubuntu. I expected the default to Budgie desktop See attached screenshot ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Tue Mar 16 10:56:53 2021 InstallationDate: Installed on 2021-03-16 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210315.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "20210316_104605.jpg" https://bugs.launchpad.net/bugs/1919313/+attachment/5477166/+files/20210316_104605.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1919313 Title: Login screen has Ubuntu and not Budgiedesktop as default Status in gdm3 package in Ubuntu: New Bug description: This occurred after installing Ubuntu Budgie Hirsute (21.04) from the daily ISO 20210315.1 The gdm package is 3.38.21-2 ubuntu 1 After installing the system and rebooting when the login screen appears the default desktop is Ubuntu. I expected the default to Budgie desktop See attached screenshot ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Tue Mar 16 10:56:53 2021 InstallationDate: Installed on 2021-03-16 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210315.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1919313/+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 1914461] [NEW] Unable to import key file in "authentication" in Software sources"
Public bug reported: Running test on Lubuntu Hirsute daily ISO from QA testing tracker http://cdimage.ubuntu.com/lubuntu/daily-live/20210203/hirsute-desktop- amd64.iso Unable to import key file in "authentication tab" - no error message received Steps to produce the bug 1. Open Software Sources from Preferences menu 2. Go to "Authentication" tab 3. Select/Click on "+Import Key File" 4. Nothing happens and no error message is received The file manager should have opened and browsed for the key to import ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: software-properties-qt 0.99.5 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Wed Feb 3 18:37:11 2021 InstallationDate: Installed on 2021-02-03 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210203) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1914461 Title: Unable to import key file in "authentication" in Software sources" Status in software-properties package in Ubuntu: New Bug description: Running test on Lubuntu Hirsute daily ISO from QA testing tracker http://cdimage.ubuntu.com/lubuntu/daily-live/20210203/hirsute-desktop- amd64.iso Unable to import key file in "authentication tab" - no error message received Steps to produce the bug 1. Open Software Sources from Preferences menu 2. Go to "Authentication" tab 3. Select/Click on "+Import Key File" 4. Nothing happens and no error message is received The file manager should have opened and browsed for the key to import ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: software-properties-qt 0.99.5 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Wed Feb 3 18:37:11 2021 InstallationDate: Installed on 2021-02-03 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210203) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1914461/+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 1875717] Re: Opening file from Samba share results in Document in Use
@wxl Walter, While testing Ubuntu 21.04 on the RASP PI4 I decided to install the Lubuntu desktop and then tried PCManFM-QT and then the opening of the Samba share files worked fine with no error messages. I then played around with a few PC boxes and got the same results after installing the Lubuntu desktop on the Ubuntu build. Ref your comments in #20 re file locks I agree - but in this case I am running a private LAN with no other users so the locked file is an incorrect message i.e these files are not in use by anyone - so either LibreOffice or PCManFM-QT are sending the wrong message to each other.. will do some further testing and comparisons with other file managers - -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1875717] Re: Opening file from Samba share results in Document in Use
Digging a bit deeper - checked out the release notes and known bugs at Libre Office and found this bit of info: Check the link below comments on Linux https://wiki.documentfoundation.org/ReleaseNotes/7.0#Configuration_changes And known bugs - https://bugs.documentfoundation.org/show_bug.cgi?id=115747 ** Bug watch added: Document Foundation Bugzilla #115747 https://bugs.documentfoundation.org/show_bug.cgi?id=115747 -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1875717] Re: Opening file from Samba share results in Document in Use
@wxl Walter Again I retested and had acloser look at your suggestion nr2 - After input: pcmanfm-qt --profile=lxqt 2>&1 I received the following messages when connecting to the Samba share and opening a file : isPrimaryInstance Icon theme "elementary" not found. shortcut is dir: smb://storhofdi.local:445/ operation finished: 0x0 delete MountOperation file monitor cannot be created: Operation not supported ask password operation finished: 0x0 delete MountOperation file monitor cannot be created: Operation not supported file monitor cannot be created: Operation not supported file monitor cannot be created: Operation not supported file monitor cannot be created: Operation not supported javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. If it is already installed then try removing ~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml Warning: failed to read path from javaldx Icon theme "elementary" not found. Any suggestions? -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1875717] Re: Opening file from Samba share results in Document in Use
@wxl Walter Ran some tests again today. 1.Connected to the Samba share manually and no problem mounting etc. Opened the share directly from LibreOffice Writer and the file came up as "read only" but this time no dialog box. 2. Proceeded onto your second suggestion - and got the same result - file opened in "read only " mode and no dialog box. Of interest is that if the share is mounted by PCManFM-Qt or thunar the file opens with the dialog box as in the original report. 3. Did not test thunar. :) -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1875717] Re: Opening file from Samba share results in Document in Use
Further testing results: 1. Ubuntu Mate Hirsute daily build 20201215 test machine Dell Inspiron 3521 a. Caja default file manager - opens files with no errors b. thunar and PCManFM-QT open files as "locked for editing..” 2. Lubuntu Hirsute daily build 20201214 test machine Lenovo x230I a. thunar and PCManFM-QT open files as "locked for editing..” b. Dolphin – opens files with no errors c. Caja and Nautilus fail to open files at all with no error messages but an unreadable flash on screen 3. Xubuntu Hirsute daily build 20201214 test machine Acer Aspire E3-111 a. thunar and PCManFM-QT open files as "locked for editing..” b. Caja and Nautilus - open files with no errors 4. Ubuntu Hirsute daily build 20201215 test machine Dell Inspiron 3521 a. Only tested the default file manager (Files) – opens files with no errors 5. Kubuntu Groovy release 20.10 test machine Acer Aspire E3-111 * a. Dolphin - opens files with no errors b. thunar and PCManFM-QT open files as "locked for editing..” * Kubuntu was tested with the Groovy release 20.10 as there are problems installing 21.04 Hirsute which is another matter altogether -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1875717] Re: Opening file from Samba share results in Document in Use
@Walter (wxl) Good questions ... I have been running tests with other file managers in Lubuntu with no success ..will also test pcmanfm-qt and thunar in one or two oth the other flavors. Will report back with more details when I finish. -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1875717] Re: Opening file from Samba share results in Document in Use
As a follow up I tested another machine running Xubuntu Hirsute and again received the "Document in use" error . My test results are here: http://iso.qa.ubuntu.com/qatracker/milestones/419/builds/224141/testcases/1300/results/ I then tested Ubuntu Budgie and was unable to reproduce the error. Also tested Kubuntu Groovy 20.10 and no error opening Samba files. So far this has then only occurred on Lubuntu and Xubuntu. Again I will reiterate that this only occurs with LibreOffice documents on the Samba share - all other applications used to open file i,e featherpad,mousepad open as normal and use the same password to access the share. -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1875717] Re: Opening file from Samba share results in Document in Use
This occurred while testing Xubuntu Hirsute daily http://cdimage.ubuntu.com/xubuntu/daily-live/20201214/hirsute-desktop- amd64.iso I used thunar the default file manager to open a file on a Samba share in Libre Office writer. Document in Use" window appears with text: Document file 'xxx.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Attached is the syslog file - see entries for 7:09 and 7:20 ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+attachment/5443355/+files/syslog -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1875717] Re: Opening file from Samba share results in Document in Use
@Walter (wxl) Sorry for the confusion - yes originally I used pcmanfm-qt as at that time the bug occurred only in Lubuntu - in all other flavors I have used their default file managers. The bug was also present in Xubuntu Hirsute daily build 20201212. I was unable to reproduce the bug in Ubuntu Hirsute and Ubuntu Mate Hirsute. I intend to test Kubuntu and Ubuntu Budgie today. -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1875717] Re: Opening file from Samba share results in Document in Use
Tested on Ubuntu and Ubuntu Mate Hirsute daily builds 13.12.2020 and could not reproduce the issue. -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1875717] Re: Opening file from Samba share results in Document in Use
** Description changed: This bug is related to bug # 1430531. - + I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. - Again this occurs only on machines with LXQt desktop. + Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1875717] Re: Opening file from Samba share results in Document in Use
I made a change to the original description as at the time I only saw this on the QT desktops. After running tests on other flavors I see that this is not the case. see comment # 5 ** Description changed: - This bug is related to bug # 1430531 however this only occurs when Libre - Office is on OS with LxQt desktop. - + This bug is related to bug # 1430531. + I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 - CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; + CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded - - 1. connect to share on local network with PCManFM-Qt File Manager - 2. click on file TEST_Samba.odt + 1. connect to share on local network with PCManFM-Qt File Manager + 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: -Document file 'TEST_Samba.odt' is locked for editing by: + Document file 'TEST_Samba.odt' is locked for editing by: -Unknown User + Unknown User -Open document read-only or open a copy of the document for editing. + Open document read-only or open a copy of the document for editing. -Open Read-Only Open Copy Cancel + Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: -The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. + The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: -User can't edit original document (see 3-5 above) + User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. - Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. + Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Again this occurs only on machines with LXQt desktop. Global Samba config is "default" - Usershare config is: + Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Again this occurs only on machines with LXQt desktop. Global Samba config is "default" Usershare config is: $ cat
[Desktop-packages] [Bug 1875717] Re: Opening file from Samba share results in Document in Use
This is unchanged in LibreOffice version 7.0.3.1 tested in dailys 12.12.2020 for Lubuntu and Xubuntu Hirsute http://cdimage.ubuntu.com/lubuntu/daily-live/20201212/hirsute-desktop- amd64.iso http://cdimage.ubuntu.com/xubuntu/daily-live/20201212/hirsute-desktop- amd64.iso Tested on 2 machines : Acer [Aspire] E3-111-P60S and Lenovo M72e i3-2120T with exactly the same results. As noted in my earlier comment # 2 this only happens in Libre Office and all other apps open/edit/save as normal. -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531 however this only occurs when Libre Office is on OS with LxQt desktop. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Again this occurs only on machines with LXQt desktop. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1905322] Re: LibreOffice crashes under load.
@seb128 Sebastien Sorry I was not clear...select LibreMarh and Librewriter from the Office menu in Lubuntu. -- 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/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) 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/1905322/+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 1905322] Re: LibreOffice crashes under load.
@hellsworth Heather Ellsworth In order to reproduce the crash this is the proceedure you need to use - 1. Open in this order - calc,draw,impress (do not select a template at this time,proceed and select math and then writer from the menu. 2. Now select the vivid template (which should be on the desktop - 3. the crash occurs I have not been able to reproduce thi unless apps opened in this order. Also I tested as per your instructions in #18 - this crash did not occur. -- 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/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) 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/1905322/+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 1905322] Re: LibreOffice crashes under load.
@seb128 -Sebastien -- the tests we did were in Lubuntu not Xubuntu .. I have only been able to preoduce this in Lubuntu Hirsute so far. Will try to run a few more tests in the other flavors. -- 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/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) 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/1905322/+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 1905322] Re: LibreOffice crashes under load.
@seb123 Sebastein Bacher I have also tested this on several machines and get the same error see my comment item 11. I tested also LibreOffice 7.02.2 running on a machine with 32GB RAM and very little running i.e 1.6 GB RAM 31GB available and get the same results. Again this happens when I select the "vivid" template but no the others. -- 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/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) 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/1905322/+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 1905322] Re: LibreOffice crashes under load.
I did some further testing on the same machine in comment #10 - I think the error is not because of the "load" but somehow related to the template selection in Impress - I noticed that when I selected the apps one by one after Impress opened with the "template selection" dialog if I did nothing and continued on to open "Math" and "Writer" they did not appear in the panel bar .I then (as in the video comment #7" selected a templete (vivid) and received the crash - if I selected a template other than "vivid" then there was no crash. Also tested but this time opened a template when "Impress" started - then no errors, no crash. Lastly I changed the Impress "select a Template dialog box - Show this dialog at startup " button and reran the tests and all worked normally. -- 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/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) 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/1905322/+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 1905322] Re: LibreOffice crashes under load.
I can confirm this bug - testing Lubuntu Hirsute daily 27.11.2020 on the QA site http://cdimage.ubuntu.com/lubuntu/daily-live/20201127/hirsute-desktop- amd64.iso Machine used Acer [Aspire] E3-111-P60S (Pent.N3530, 4GB) Opened all LibreOffice apps one by one and selected Impress templete "Vivid" as in the video posted in comment # 7 and received the same results as KGIII. -- 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/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) 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/1905322/+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 1892637] Re: Printing a blank page with libreoffice on Lubuntu 20.04
Looked further into this and the solution is 2 add these 2 lines to the LXQt session settings environmental variables Variable name Value SAL_USE_VCLPLUGIN qt5 SAL_VCL_QT5_USE_CAIRO true -- 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/1892637 Title: Printing a blank page with libreoffice on Lubuntu 20.04 Status in libreoffice package in Ubuntu: Confirmed Bug description: Hello maintainer, Printing from libreoffice on Lubuntu 20.04 allways produces a blank page. After removing the package libreoffice-qt5 it works. To reproducing the bug, you do not need to install a real printer. Having the package printer-driver-cups-pdf install is enough. Release Lubuntu 20.04.1 LTS libreoffice-qt5 1:6.4.5-0ubuntu0.20.04.1 Regards Reiner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892637/+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 1892637] Re: Printing a blank page with libreoffice on Lubuntu 20.04
Tested on Lubuntu 20.04.1 LTS and Groovy Lubuntu daily ISO 20200930 and can confirm this. As a workaround run in terminal: sudo apt install libreoffice-kf5 followed by: sudo apt remove libreoffice-qt5 I refer to https://ask.libreoffice.org/en/question/242188/cannot-print-anything-exporting-to-pdf-produces-blank-pdf-lubuntu-2004/ this needs further testing as there maybe adverse effects which I am not aware of. -- 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/1892637 Title: Printing a blank page with libreoffice on Lubuntu 20.04 Status in libreoffice package in Ubuntu: Confirmed Bug description: Hello maintainer, Printing from libreoffice on Lubuntu 20.04 allways produces a blank page. After removing the package libreoffice-qt5 it works. To reproducing the bug, you do not need to install a real printer. Having the package printer-driver-cups-pdf install is enough. Release Lubuntu 20.04.1 LTS libreoffice-qt5 1:6.4.5-0ubuntu0.20.04.1 Regards Reiner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892637/+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 1875717] Re: Opening file from Samba share results in Document in Use
This is unchanged in LibreOffice version 6.4.3.2 Build ID 1:6.4.3-0ubuntu0.20.04.1 on Lubuntu 20.04. - again this only happens in Libre Office and all other apps open/edit/save as normal. -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531 however this only occurs when Libre Office is on OS with LxQt desktop. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Again this occurs only on machines with LXQt desktop. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1869561] Re: Libreoffice Help does not work
I tested this yesterday 05.05.2020 on the daily builds for Groovy on Lubuntu,Xubuntu,Kubuntu and Ubuntu ISO´s and can also nconfirm this is still present in version 6.4.3.2 in all of the forementioned. -- 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/1869561 Title: Libreoffice Help does not work Status in libreoffice package in Ubuntu: Confirmed Status in libreoffice source package in Focal: Confirmed Bug description: In the latest PPA release of Libreoffice, the Help does not work. IN version 6.3.5.2 it is OK. I the version below it returns an error. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.19.10.3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Error is: Object not accessible. The object cannot be accessed due to insufficient user rights. The Help used to open the help in a browser window. This latest version seems to try to open the old type of local help (rather than using a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+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 1876701] [NEW] Unable to access help text in LibreOffice 6.4.2.2
*** This bug is a duplicate of bug 1869561 *** https://bugs.launchpad.net/bugs/1869561 Public bug reported: Unable to access help text in Libre Office 6.4.2.2 when selecting F1 or by selecting from the menu LibreOffice help Expected results = help text Actual result is the following response: Object not accessible. The object cannot be accessed due to insufficient user rights. Version 6..4.2.2 running on Lubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon May 4 10:09:57 2020 InstallationDate: Installed on 2020-05-04 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1876701 Title: Unable to access help text in LibreOffice 6.4.2.2 Status in libreoffice package in Ubuntu: New Bug description: Unable to access help text in Libre Office 6.4.2.2 when selecting F1 or by selecting from the menu LibreOffice help Expected results = help text Actual result is the following response: Object not accessible. The object cannot be accessed due to insufficient user rights. Version 6..4.2.2 running on Lubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon May 4 10:09:57 2020 InstallationDate: Installed on 2020-05-04 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1876701/+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 1875717] Re: Opening file from Samba share results in Document in Use
Following up on my original report here are the entries from my syslog on the client requesting to open the file and when that fails requesting to open a copy which succeeds -- again this only happens in Libre Office and all other apps open/edit/save as normal. See attached file syslog_OL.txt ** Attachment added: "syslog_OL.txt" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+attachment/5363216/+files/syslog_OL.txt -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531 however this only occurs when Libre Office is on OS with LxQt desktop. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Again this occurs only on machines with LXQt desktop. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875717/+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 1875717] [NEW] Opening file from Samba share results in Document in Use
Public bug reported: This bug is related to bug # 1430531 however this only occurs when Libre Office is on OS with LxQt desktop. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Again this occurs only on machines with LXQt desktop. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screen.jpg" https://bugs.launchpad.net/bugs/1875717/+attachment/5362782/+files/screen.jpg -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531 however this only occurs when Libre Office is on OS with LxQt desktop. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Again this occurs only on machines with LXQt desktop. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage
[Desktop-packages] [Bug 1873685] Re: Wallpaper not updated to 20.04 default after upgrade
Attached is the apport.lubuntu-artwork file ** Attachment added: "apport.lubuntu-artwork.dnc1a_x_.apport" https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1873685/+attachment/5356851/+files/apport.lubuntu-artwork.dnc1a_x_.apport -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1873685 Title: Wallpaper not updated to 20.04 default after upgrade Status in Lubuntu Artwork: New Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Wallpaper not updated to 20.04 default after upgrade. After GUI upgrade from Lubuntu version 19.10 to Lubuntu Focal 20.04 the desktop still showing the 19.10 default wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-wallpapers-focal (not installed) ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Apr 19 17:44:01 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) SourcePackage: ubuntu-wallpapers UpgradeStatus: Upgraded to focal on 2020-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-artwork/+bug/1873685/+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 1873685] Re: Wallpaper not updated to 20.04 default after upgrade
** Also affects: lubuntu-artwork Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1873685 Title: Wallpaper not updated to 20.04 default after upgrade Status in Lubuntu Artwork: New Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Wallpaper not updated to 20.04 default after upgrade. After GUI upgrade from Lubuntu version 19.10 to Lubuntu Focal 20.04 the desktop still showing the 19.10 default wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-wallpapers-focal (not installed) ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Apr 19 17:44:01 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) SourcePackage: ubuntu-wallpapers UpgradeStatus: Upgraded to focal on 2020-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-artwork/+bug/1873685/+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 1873685] [NEW] Wallpaper not updated to 20.04 default after upgrade
Public bug reported: Wallpaper not updated to 20.04 default after upgrade. After GUI upgrade from Lubuntu version 19.10 to Lubuntu Focal 20.04 the desktop still showing the 19.10 default wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-wallpapers-focal (not installed) ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Apr 19 17:44:01 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) SourcePackage: ubuntu-wallpapers UpgradeStatus: Upgraded to focal on 2020-04-19 (0 days ago) ** Affects: ubuntu-wallpapers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1873685 Title: Wallpaper not updated to 20.04 default after upgrade Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Wallpaper not updated to 20.04 default after upgrade. After GUI upgrade from Lubuntu version 19.10 to Lubuntu Focal 20.04 the desktop still showing the 19.10 default wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-wallpapers-focal (not installed) ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Apr 19 17:44:01 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) SourcePackage: ubuntu-wallpapers UpgradeStatus: Upgraded to focal on 2020-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1873685/+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 1873360] [NEW] Ethernet driver not loaded at boot
Public bug reported: Running a test on Focal Daily build 16.04.2020 the ethernet driver was not loaded at boot - attached is the dmesg.log - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1873360/+attachment/5355779/+files/dmesg -- 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/1873360 Title: Ethernet driver not loaded at boot Status in network-manager package in Ubuntu: New Bug description: Running a test on Focal Daily build 16.04.2020 the ethernet driver was not loaded at boot - attached is the dmesg.log - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1873360/+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 1864526] Re: Display ghosting when dragging icons or opening menus
Further to my initial report -- I have also tested with another monitor Dell U3419W with the same results. -- 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/1864526 Title: Display ghosting when dragging icons or opening menus Status in xorg package in Ubuntu: New Bug description: Display ghosting when dragging icons or opening menus. Have tested several machines and this only occurring on Intel NUC 8i3BEK - and only when installing or using FOCAL Lubuntu 20.04 . This also is occurring in the Live sessions before install. I have tested Lubuntu Eoan 19.01 and Lubuntu Bionic 18.04.04 on this machine and cannot reproduce the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: LXQt Date: Mon Feb 24 18:23:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200224) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 001 Device 002: ID 2188:0ae1 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=11c10d68-db79-4d45-9bbe-8357e125b46b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0073.2019.0618.1409 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-307 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0073.2019.0618.1409:bd06/18/2019:svnIntel(R)ClientSystems:pnNUC8i3BEK:pvrJ72748-306:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-307:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BE dmi.product.name: NUC8i3BEK dmi.product.sku: BOXNUC8i3BEK dmi.product.version: J72748-306 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864526/+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 1864526] [NEW] Display ghosting when dragging icons or opening menus
Public bug reported: Display ghosting when dragging icons or opening menus. Have tested several machines and this only occurring on Intel NUC 8i3BEK - and only when installing or using FOCAL Lubuntu 20.04 . This also is occurring in the Live sessions before install. I have tested Lubuntu Eoan 19.01 and Lubuntu Bionic 18.04.04 on this machine and cannot reproduce the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: LXQt Date: Mon Feb 24 18:23:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200224) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 001 Device 002: ID 2188:0ae1 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=11c10d68-db79-4d45-9bbe-8357e125b46b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0073.2019.0618.1409 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-307 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0073.2019.0618.1409:bd06/18/2019:svnIntel(R)ClientSystems:pnNUC8i3BEK:pvrJ72748-306:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-307:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BE dmi.product.name: NUC8i3BEK dmi.product.sku: BOXNUC8i3BEK dmi.product.version: J72748-306 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal reproducible 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/1864526 Title: Display ghosting when dragging icons or opening menus Status in xorg package in Ubuntu: New Bug description: Display ghosting when dragging icons or opening menus. Have tested several machines and this only occurring on Intel NUC 8i3BEK - and only when installing or using FOCAL Lubuntu 20.04 . This also is occurring in the Live sessions before install. I have tested Lubuntu Eoan 19.01 and Lubuntu Bionic 18.04.04 on this machine and cannot reproduce the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: LXQt Date: Mon Feb 24 18:23:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200224) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 001 Device 002: ID 2188:0ae1 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic
[Desktop-packages] [Bug 1851221] [NEW] localized language (Icelandic) incomplete
Public bug reported: Localized language (Icelandic) incomplete - the system not fully localized. This occurred testing Kubuntu Focal Desktop daily build 20191104. Many pages/texts are mixed with both English and Icelandic The calendar settings show the regional settings correctly. ** Affects: language-selector (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1851221 Title: localized language (Icelandic) incomplete Status in language-selector package in Ubuntu: New Bug description: Localized language (Icelandic) incomplete - the system not fully localized. This occurred testing Kubuntu Focal Desktop daily build 20191104. Many pages/texts are mixed with both English and Icelandic The calendar settings show the regional settings correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1851221/+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 1815354] Re: BCM 43142 driver not installed - no WiFi
I would like to add that this is a major problem for anyone running a machine with no ethernet attached.Upon install of the OS the Lubuntu installer states " This computer does not satisfy some of the recommended requirements for installing Lubuntu 19.04 " "the system is not connected to the internet." For obvious reasons a machine that cannot connect to the internet is useless. I am aware that this is not a problem of the network manager but feel strongly that the drivers should be included in the installation media. -- 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/1815354 Title: BCM 43142 driver not installed - no WiFi Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Disco daily Lubuntu 09.02.2019 and Disco daily Kubuntu 10.02.2019 BCM 43142 drivers not installed resulting in no WiFi during and after installation. I was able to attach ethernet cable and use the command line "ubuntu- drivers" command to install the drivers and all worked well after that. Of course if running a machine with no ethernet then this is a huge problem for the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1815354/+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 1811540] Re: gvfsd-trash crashed with SIGSEGV in trash_item_invoke_closure()
Tested today build 25.02.19 daily tests and was unable to repeat the error--changing icon size worked well for me. This was tested Live on a Dell laptop not in a virtual machine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1811540 Title: gvfsd-trash crashed with SIGSEGV in trash_item_invoke_closure() Status in gvfs package in Ubuntu: New Bug description: I started a live session using daily ISO 20190112 within KVM. I opened the Settings application, changed the Ubuntu dock icon size and when I closed Settings I saw a crash notification which led to the reporting of this bug report. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gvfs-daemons 1.38.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CasperVersion: 1.401 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 12 21:34:16 2019 Disassembly: => 0x50: Cannot access memory at address 0x50 ExecutablePath: /usr/lib/gvfs/gvfsd-trash LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190112) ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.27 /org/gtk/gvfs/exec_spaw/1 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x50: Cannot access memory at address 0x50 PC (0x0050) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () ?? () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gvfsd-trash crashed with SIGSEGV in g_closure_invoke() 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/ubuntu/+source/gvfs/+bug/1811540/+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 1815354] [NEW] BCM 43142 driver not installed - no WiFi
Public bug reported: Disco daily Lubuntu 09.02.2019 and Disco daily Kubuntu 10.02.2019 BCM 43142 drivers not installed resulting in no WiFi during and after installation. I was able to attach ethernet cable and use the command line "ubuntu- drivers" command to install the drivers and all worked well after that. Of course if running a machine with no ethernet then this is a huge problem for the user. ** Affects: network-manager (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/1815354 Title: BCM 43142 driver not installed - no WiFi Status in network-manager package in Ubuntu: New Bug description: Disco daily Lubuntu 09.02.2019 and Disco daily Kubuntu 10.02.2019 BCM 43142 drivers not installed resulting in no WiFi during and after installation. I was able to attach ethernet cable and use the command line "ubuntu- drivers" command to install the drivers and all worked well after that. Of course if running a machine with no ethernet then this is a huge problem for the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815354/+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
