[Desktop-packages] [Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
This bug was fixed in the package libcanberra - 0.30-10ubuntu1 --- libcanberra (0.30-10ubuntu1) jammy; urgency=medium * Merge with debian, remaining changes: - Disable login sound by default and hide sound from startup applications - Install the gtk plugin in the unity-settings-daemon dir * debian/gbp.conf: Update with ubuntu settings * debian/control: Update reference to ubuntu branches * debian/changelog: Add missing entries lost during merges * debian/changelog: Fix Heather's email address * debian/patches: Refresh libcanberra (0.30-10) unstable; urgency=medium * debian/patches/gtk_dont_assume_x11.patch: Avoid more X11-only codepaths libcanberra (0.30-9) unstable; urgency=medium * debian/patches: Refresh * debian/patches: Handle display closing gracefully (LP: #1949200) -- Marco Trevisan (Treviño) Sat, 09 Apr 2022 01:34:34 +0200 ** Changed in: libcanberra (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Won't Fix Status in libcanberra package in Ubuntu: Fix Released Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4 This seems to be a result of Xwayland crashing and gnome-shell then trying to recover (and failing). Although gnome-shell shouldn't be using GTK, and Wayland sessions shouldn't be dependent on having an X11 server (Xwayland) available. Fixing either of those should resolve this. WORKAROUND: sudo apt remove libcanberra-gtk3-module TEST CASE: 1. Log into a Wayland session. 2. Open a Terminal. 3. $ xrandr # Just to ensure Xwayland starts 4. $ killall Xwayland Expected: gnome-shell still responds. Observed: gnome-shell freezes or exits. --- ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() 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/1949200/+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 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
try boot kernel 5.15.0-23-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS Status in wpa package in Ubuntu: Confirmed Bug description: Using the current beta of Jammy, I no longer have stable WiFi after April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There is a chance it may also be related to network-manager going from 1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to wpasupplicant (see below) Wifi is stable often, but also often it fails to load webpages intermittently or fails to download the packages using apt for example, so it's not browser related. Example output of journalctl -xe -u wpasupplicant: Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1 Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with fc:34:97:23:4c:3c Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-94 txrate=27 Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=-95 txrate=27 Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying completed with fc:34:97:23:4c:3c [GTK=CCMP] Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-95 txrate=243000 Additional info: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy wpasupplicant wpasupplicant: Geïnstalleerd: 2:2.10-6 Kandidaat: 2:2.10-6 Versietabel: *** 2:2.10-6 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 8 21:28:12 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-03-12 (27 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220311) SourcePackage: wpa
[Desktop-packages] [Bug 1960265] Re: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1960265 Title: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in chromium-browser package in Ubuntu: Expired Bug description: chromium browser install problem while ubuntu release upgrade from 18.04 lts to 20.04 lts ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 Uname: Linux 4.9.253-tegra aarch64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: arm64 Date: Mon Feb 7 19:41:24 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstalledPlugins: Load-Avg-1min: 1.67 Load-Processes-Running-Percent: 0.1% ProcKernelCmdLine: console=ttyTCU0,115200 video=tegrafb earlycon=tegra_comb_uart,mmio32,0x0c168000 gpt rootfs.slot_suffix= usbcore.old_scheme_first=1 tegraid=19.1.2.0.0 maxcpus=6 boot.slot_suffix=_b boot.ratchetvalues=0.4.2 vpr_resize sdhci_tegra.en_boot_part_access=1quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2022-02-07 (0 days ago) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1960265/+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 1968451] [NEW] GNOME launcher folder icons and labels very small
Public bug reported: Ubuntu 22.04 Daily Build from April 9th The default Utilities folder in GNOME Shell applications launcher (the screen that shows when you hit Super twice) are extremely small/tiny. I haven't seen this with other versions of GNOME shell on other distros with this version of GNOME that I have tested, so it may be a Ubuntu specific issue. I've attached a screenshot of the "Utilities" folder as it existed by default after install, I did however change the icon theme to a few different ones before noticing, but it persisted after switching back to Yaru Icon Theme. I was able to get the normal behavior by dragging all the icons out one by one and recreating the folder, after which it appears normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 21:11:51 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Untitled.png" https://bugs.launchpad.net/bugs/1968451/+attachment/5578879/+files/Untitled.png -- 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/1968451 Title: GNOME launcher folder icons and labels very small Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 Daily Build from April 9th The default Utilities folder in GNOME Shell applications launcher (the screen that shows when you hit Super twice) are extremely small/tiny. I haven't seen this with other versions of GNOME shell on other distros with this version of GNOME that I have tested, so it may be a Ubuntu specific issue. I've attached a screenshot of the "Utilities" folder as it existed by default after install, I did however change the icon theme to a few different ones before noticing, but it persisted after switching back to Yaru Icon Theme. I was able to get the normal behavior by dragging all the icons out one by one and recreating the folder, after which it appears normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 21:11:51 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968451/+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 1946575] Re: Maybe a bug with the standby timer / sleep mode timer for HDDs
** Description changed: Hallo, - the standby timer for HDDs is maybe a little bit broken. + the standby timer for HDDs may be a little bit broken. It works fine if I set it to 8 minutes or less. If I set it 10 minutes or above the timer does not send the HDDs to standby any more. I tested also 12, 15 and 20 minutes. Every time above 10 minutes does not work. The HDDs are two Samsung Spinpoint HDDs, just for Data. There are no active programs on them and it does not matter, if the HDDs are mounted or not. In both cases it is the same behavior. It has been like this since installation, so I don't think that other software is interfering the timer process. Maybe you have already fixed it in a newer version, but I just wanted to tell you this behavior. I use gnome-disk-utility 3.36.3-0ubuntu1 on Ubuntu 20.04.3 LTS Release: 20.04. Thanks for your attention and your great work. Kind regards Chris ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 9 21:31:39 2021 InstallationDate: Installed on 2021-09-16 (22 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility 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 gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1946575 Title: Maybe a bug with the standby timer / sleep mode timer for HDDs Status in gnome-disk-utility package in Ubuntu: New Bug description: Hallo, the standby timer for HDDs may be a little bit broken. It works fine if I set it to 8 minutes or less. If I set it 10 minutes or above the timer does not send the HDDs to standby any more. I tested also 12, 15 and 20 minutes. Every time above 10 minutes does not work. The HDDs are two Samsung Spinpoint HDDs, just for Data. There are no active programs on them and it does not matter, if the HDDs are mounted or not. In both cases it is the same behavior. It has been like this since installation, so I don't think that other software is interfering the timer process. Maybe you have already fixed it in a newer version, but I just wanted to tell you this behavior. I use gnome-disk-utility 3.36.3-0ubuntu1 on Ubuntu 20.04.3 LTS Release: 20.04. Thanks for your attention and your great work. Kind regards Chris ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 9 21:31:39 2021 InstallationDate: Installed on 2021-09-16 (22 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1946575/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
** Bug watch added: github.com/woodruffw/ff2mpv/issues #80 https://github.com/woodruffw/ff2mpv/issues/80 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 1840473] Re: Don't draw | character on the screen while key is typed. :-)
** Bug watch added: Red Hat Bugzilla #1861305 https://bugzilla.redhat.com/show_bug.cgi?id=1861305 ** Bug watch added: Red Hat Bugzilla #1733599 https://bugzilla.redhat.com/show_bug.cgi?id=1733599 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) Status in xorg-server package in Ubuntu: Invalid Status in xfwm4 package in Fedora: Invalid Bug description: Edit: more padding. Problem: don't draw | on the screen, it makes no sense! :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+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 1840473]
Don't animate character "|" while typing. 1. a (while typing) 2. a| (after pressing) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) Status in xorg-server package in Ubuntu: Invalid Status in xfwm4 package in Fedora: Invalid Bug description: Edit: more padding. Problem: don't draw | on the screen, it makes no sense! :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+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 1840473]
I am going to close this as NOTABUG since it is unclear what the issue really is. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) Status in xorg-server package in Ubuntu: Invalid Status in xfwm4 package in Fedora: Invalid Bug description: Edit: more padding. Problem: don't draw | on the screen, it makes no sense! :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+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 1840473]
Actually this looks like "Doesn't have space for next character" problem. Obviously not only XFCE is affected. How can this be solved cleverly? |? :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) Status in xorg-server package in Ubuntu: Invalid Status in xfwm4 package in Fedora: Invalid Bug description: Edit: more padding. Problem: don't draw | on the screen, it makes no sense! :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+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 1840473]
No. Problem is with positioning of "|" character. I am not sure how to improve this unfortunately. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) Status in xorg-server package in Ubuntu: Invalid Status in xfwm4 package in Fedora: Invalid Bug description: Edit: more padding. Problem: don't draw | on the screen, it makes no sense! :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+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 1741074]
Chiming in as a maintainer of an extension ([ff2mpv](https://github.com/woodruffw/ff2mpv)) that uses native messaging: users have already reported challenges getting the extension to function correctly with the `snap`-ified Firefox distribution in the upcoming Ubuntu LTS release. Downstream tracking: https://github.com/woodruffw/ff2mpv/issues/80 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 1840473]
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) Status in xorg-server package in Ubuntu: Invalid Status in xfwm4 package in Fedora: Invalid Bug description: Edit: more padding. Problem: don't draw | on the screen, it makes no sense! :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+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 1840473]
Hide | character while any key is pressed. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) Status in xorg-server package in Ubuntu: Invalid Status in xfwm4 package in Fedora: Invalid Bug description: Edit: more padding. Problem: don't draw | on the screen, it makes no sense! :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+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 1840473]
Same problem. Action is preceding typed character and this breaks the workflow. @ https://bugzilla.redhat.com/show_bug.cgi?id=1733599#c21 :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) Status in xorg-server package in Ubuntu: Invalid Status in xfwm4 package in Fedora: Invalid Bug description: Edit: more padding. Problem: don't draw | on the screen, it makes no sense! :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+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 1840473]
Created attachment 1703241 bug 1861305 Hi, this has to do with how responsive is typing itself. Something makes keyboard unresponsive, pls take a look here: https://bugzilla.redhat.com/show_bug.cgi?id=1861305 Sry for mistake! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) Status in xorg-server package in Ubuntu: Invalid Status in xfwm4 package in Fedora: Invalid Bug description: Edit: more padding. Problem: don't draw | on the screen, it makes no sense! :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+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 1840473]
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) Status in xorg-server package in Ubuntu: Invalid Status in xfwm4 package in Fedora: Invalid Bug description: Edit: more padding. Problem: don't draw | on the screen, it makes no sense! :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+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 1968449] Re: gnome-control-center crashed with SIGSEGV trying to add a google account
*** This bug is a duplicate of bug 1965702 *** https://bugs.launchpad.net/bugs/1965702 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1965702, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968449/+attachment/5578868/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1968449/+attachment/5578870/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1968449/+attachment/5578874/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1968449/+attachment/5578875/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1968449/+attachment/5578876/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1968449/+attachment/5578877/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968449/+attachment/5578878/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1965702 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1968449 Title: gnome-control-center crashed with SIGSEGV trying to add a google account Status in gnome-control-center package in Ubuntu: New Bug description: Trying to add any cloud based Online Account, like Google or Microsoft, that require to open a webkit window for html based login, the panel crashes right away before showing the webkit window. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu10 Uname: Linux 5.17.1-051701-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 10 01:41:35 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-31 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7fec56ac92eb:mov0x8,%rax PC (0x7fec56ac92eb) ok source "0x8" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 () at /lib/x86_64-linux-gnu/libffi.so.8 () at /lib/x86_64-linux-gnu/libffi.so.8 () at /lib/x86_64-linux-gnu/libwayland-server.so.0 () at /lib/x86_64-linux-gnu/libwayland-server.so.0 Title: gnome-control-center 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-control-center/+bug/1968449/+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 1959508] Re: enable BMFF support in exiv2
** Changed in: exiv2 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1959508 Title: enable BMFF support in exiv2 Status in exiv2 package in Ubuntu: Confirmed Status in exiv2 package in Debian: Fix Released Bug description: On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that Ubuntu 22.04 currently includes exiv2 0.27.3 Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3 file format has been the Canon camera-raw file format since mid 2018, and is probably one of the most common raw image file formats today. Applications such as darktable, amongst others, use exiv2 to extract image metadata, thumbnails and previews, and can only open CR3 files when linked with exiv2 0.27.5 or later. Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On to enable *.CR3 support. Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled included in Ubuntu 22.04? Note that a similar request exists for Debian in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788 References https://github.com/exiv2/exiv2#2-19 https://github.com/Exiv2/exiv2/issues/1229 https://github.com/darktable-org/darktable/pull/10332 https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918 https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+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 1968448] [NEW] package libxslt1.1:i386 1.1.34-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: Hi ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libxslt1.1:i386 1.1.34-4 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 9 11:46:28 2022 DuplicateSignature: package:libxslt1.1:i386:1.1.34-4 Setting up mesa-utils (8.4.0-1build1) ... dpkg: error processing package libxslt1.1:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: libxslt Title: package libxslt1.1:i386 1.1.34-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxslt (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package focal i386 need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxslt in Ubuntu. https://bugs.launchpad.net/bugs/1968448 Title: package libxslt1.1:i386 1.1.34-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxslt package in Ubuntu: New Bug description: Hi ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libxslt1.1:i386 1.1.34-4 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 9 11:46:28 2022 DuplicateSignature: package:libxslt1.1:i386:1.1.34-4 Setting up mesa-utils (8.4.0-1build1) ... dpkg: error processing package libxslt1.1:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: libxslt Title: package libxslt1.1:i386 1.1.34-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1968448/+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 1946575] Re: Maybe a bug with the standby timer / sleep mode timer for HDDs
** Description changed: Hallo, the standby timer for HDDs is maybe a little bit broken. It works fine if I set it to 8 minutes or less. If I set it 10 minutes or above the timer does not send the HDDs to standby any more. - I tested also 12, 15 and 20 minutes. Every time about 10 minutes does not work. + I tested also 12, 15 and 20 minutes. Every time above 10 minutes does not work. The HDDs are two Samsung Spinpoint HDDs, just for Data. - There are no active programms on them and it does not matter, if the HDDs are mounted or not. In both cases it is the same behavior. + There are no active programs on them and it does not matter, if the HDDs are mounted or not. In both cases it is the same behavior. It has been like this since installation, so I don't think that other software is interfering the timer process. Maybe you have already fixed it in a newer version, but I just wanted to tell you this behavior. I use gnome-disk-utility 3.36.3-0ubuntu1 on Ubuntu 20.04.3 LTS Release: 20.04. - + Thanks for your attention and your great work. Kind regards Chris ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 9 21:31:39 2021 InstallationDate: Installed on 2021-09-16 (22 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility 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 gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1946575 Title: Maybe a bug with the standby timer / sleep mode timer for HDDs Status in gnome-disk-utility package in Ubuntu: New Bug description: Hallo, the standby timer for HDDs is maybe a little bit broken. It works fine if I set it to 8 minutes or less. If I set it 10 minutes or above the timer does not send the HDDs to standby any more. I tested also 12, 15 and 20 minutes. Every time above 10 minutes does not work. The HDDs are two Samsung Spinpoint HDDs, just for Data. There are no active programs on them and it does not matter, if the HDDs are mounted or not. In both cases it is the same behavior. It has been like this since installation, so I don't think that other software is interfering the timer process. Maybe you have already fixed it in a newer version, but I just wanted to tell you this behavior. I use gnome-disk-utility 3.36.3-0ubuntu1 on Ubuntu 20.04.3 LTS Release: 20.04. Thanks for your attention and your great work. Kind regards Chris ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 9 21:31:39 2021 InstallationDate: Installed on 2021-09-16 (22 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1946575/+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 1968447] Re: Unity's fcitx integration has become obsolete
@Aron: If I recall correctly, you were heavily involved in implementing the fcitx integration. Do you have any thoughts on the best way to handle it now? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1968447 Title: Unity's fcitx integration has become obsolete Status in unity-control-center package in Ubuntu: New Bug description: Unity integrates both ibus and fcitx. At least it used to. What I mean by that is that if you use e.g. fcitx, you can manage also fcitx input sources from Text Entry, and no Fcitx icon is shown in the top bar. But time goes by, and the version of fcitx supported by Unity (fcitx 4) is deprecated and replaced by fcitx 5. As from Ubuntu 21.10 language-selector-common pulls fcitx 5 for Chinese users instead of fcitx 4. So something should be done about this. I can think of two options: 1. Adapt the fcitx integration to work with fcitx 5. 2. Drop the fcitx integration, and let fcitx 5 do its thing alongside Text Entry etc. I chose to submit this bug against unity-control-center, but I'm pretty sure that more packages are affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1968447/+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 1968447] [NEW] Unity's fcitx integration has become obsolete
Public bug reported: Unity integrates both ibus and fcitx. At least it used to. What I mean by that is that if you use e.g. fcitx, you can manage also fcitx input sources from Text Entry, and no Fcitx icon is shown in the top bar. But time goes by, and the version of fcitx supported by Unity (fcitx 4) is deprecated and replaced by fcitx 5. As from Ubuntu 21.10 language- selector-common pulls fcitx 5 for Chinese users instead of fcitx 4. So something should be done about this. I can think of two options: 1. Adapt the fcitx integration to work with fcitx 5. 2. Drop the fcitx integration, and let fcitx 5 do its thing alongside Text Entry etc. I chose to submit this bug against unity-control-center, but I'm pretty sure that more packages are affected. ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1968447 Title: Unity's fcitx integration has become obsolete Status in unity-control-center package in Ubuntu: New Bug description: Unity integrates both ibus and fcitx. At least it used to. What I mean by that is that if you use e.g. fcitx, you can manage also fcitx input sources from Text Entry, and no Fcitx icon is shown in the top bar. But time goes by, and the version of fcitx supported by Unity (fcitx 4) is deprecated and replaced by fcitx 5. As from Ubuntu 21.10 language-selector-common pulls fcitx 5 for Chinese users instead of fcitx 4. So something should be done about this. I can think of two options: 1. Adapt the fcitx integration to work with fcitx 5. 2. Drop the fcitx integration, and let fcitx 5 do its thing alongside Text Entry etc. I chose to submit this bug against unity-control-center, but I'm pretty sure that more packages are affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1968447/+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 1754125] Re: Rhythmbox stays running in the background after quit
This Bug affects me too. I am using Ubuntu 20.04. LTS The strange thing is, that quitting Rhythmbox with Ctrl+Q works perfect in my superuser account, which I use for system administration. But in my standard user account, which I use for internet browsing, etc., I can not quit Rhythmbox with Ctrl+Q. In my standard user account I am facing the same bug as described here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1754125 Title: Rhythmbox stays running in the background after quit Status in rhythmbox package in Ubuntu: Triaged Bug description: If you do ps -alx you will see rhythmbox process still running. It causes opening rhythmbox to hang when trying to open again ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 7 13:21:51 2018 InstallationDate: Installed on 2018-03-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
Minor update: when the WiFi is being flaky, I often get see 100% CPU usage for ksoftirqd, but not always. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS Status in wpa package in Ubuntu: Confirmed Bug description: Using the current beta of Jammy, I no longer have stable WiFi after April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There is a chance it may also be related to network-manager going from 1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to wpasupplicant (see below) Wifi is stable often, but also often it fails to load webpages intermittently or fails to download the packages using apt for example, so it's not browser related. Example output of journalctl -xe -u wpasupplicant: Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1 Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with fc:34:97:23:4c:3c Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-94 txrate=27 Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=-95 txrate=27 Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying completed with fc:34:97:23:4c:3c [GTK=CCMP] Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-95 txrate=243000 Additional info: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy wpasupplicant wpasupplicant: Geïnstalleerd: 2:2.10-6 Kandidaat: 2:2.10-6 Versietabel: *** 2:2.10-6 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 8 21:28:12 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-03-12 (27 days ago) InstallationMedia: Kubuntu 22.
[Desktop-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled via gnome-system-tools
This bug was fixed in the package ubuntu-mate-meta - 1.282 --- ubuntu-mate-meta (1.282) jammy; urgency=medium * Refreshed dependencies * Removed gnome-system-tools from core-recommends, desktop-recommends (LP: #1706770) -- Martin Wimpress Sat, 09 Apr 2022 01:01:57 +0100 ** Changed in: ubuntu-mate-meta (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled via gnome- system-tools Status in arctica-greeter package in Ubuntu: Invalid Status in gnome-system-tools package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Invalid Status in mate-screensaver package in Ubuntu: Invalid Status in mate-session-manager package in Ubuntu: Invalid Status in ubuntu-mate-meta package in Ubuntu: Fix Released Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1706770/+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 1968213] Re: Icon theme reverts to Yaru when entering Appearance settings
It does also revert the theme of some system apps. 1. Open gedit 2. Go to preferences 3. Select the desired theme under Fonts & Colors (non-Yaru) 4. Go into Appearance settings in the settings app. 5. Reopen gedit and the theme will be Yaru. I think the main issue is that the theme reverts to Yaru even if no settings are changed. It is understandable that selecting a new accent color reverts to the appropriate Yaru theme, but if no settings are changes, then why does it do that? -- 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/1968213 Title: Icon theme reverts to Yaru when entering Appearance settings Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I upgraded to the 22.04 beta last week from 21.10. I use a custom icon theme. Whenever I enter the Appearance tab in settings the icon theme is set back to Yaru. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu9 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 20:47:41 2022 InstallationDate: Installed on 2022-02-02 (64 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968213/+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 1965636] Re: libfuse2 no longer included in jammy, required for AppImages
** Also affects: ubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: kubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: xubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: ubuntustudio-meta (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: lubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: ubuntukylin-meta (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: ubuntu-budgie-meta (Ubuntu Jammy) Importance: Undecided Status: Fix Released -- 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/1965636 Title: libfuse2 no longer included in jammy, required for AppImages Status in kubuntu-meta package in Ubuntu: Fix Released Status in lubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-budgie-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntukylin-meta package in Ubuntu: Confirmed Status in ubuntustudio-meta package in Ubuntu: Fix Released Status in xubuntu-meta package in Ubuntu: Fix Released Status in kubuntu-meta source package in Jammy: Fix Released Status in lubuntu-meta source package in Jammy: Confirmed Status in ubuntu-budgie-meta source package in Jammy: Fix Released Status in ubuntu-meta source package in Jammy: Confirmed Status in ubuntukylin-meta source package in Jammy: Confirmed Status in ubuntustudio-meta source package in Jammy: Fix Released Status in xubuntu-meta source package in Jammy: Fix Released Bug description: Attempting to run an AppImage in Xubuntu 22.04 displays the following error: $ ./cryptomator-1.6.5-x86_64.AppImage dlopen(): error loading libfuse.so.2 AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information --- Simply installing libfuse2 resolves this issue. Some flavors seem to still include it. I noticed that today's Ubuntu MATE daily still does. Ubuntu and Xubuntu do not. Ubuntu: https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.manifest Xubuntu: https://cdimage.ubuntu.com/xubuntu/daily-live/current/jammy-desktop-amd64.manifest Ubuntu MATE: https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.manifest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1965636/+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 1968440] Re: gjs-console assert failure: free(): invalid pointer
*** This bug is a duplicate of bug 1946165 *** https://bugs.launchpad.net/bugs/1946165 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1946165, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968440/+attachment/5578803/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1968440/+attachment/5578805/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1968440/+attachment/5578809/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1968440/+attachment/5578810/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1968440/+attachment/5578811/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1968440/+attachment/5578812/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968440/+attachment/5578813/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1946165 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1968440 Title: gjs-console assert failure: free(): invalid pointer Status in gjs package in Ubuntu: New Bug description: I was browsing the web and this popup came up saying that gjs-console had stopped working. My system specs OS: Ubuntu 22.04 lts beta Processor: Intel Core i5-4220M GPU: IntelHD 4600 RAM: 16Gigs Gnomeversion: 42 Windowsing system: Wayland. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gjs 1.72.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AssertionMessage: free(): invalid pointer CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 10 01:00:37 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Extensions RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: gjs StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8b3637ab8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f8b36378764 "free(): invalid pointer") at ./malloc/malloc.c:5664 _int_free (av=, p=, have_lock=0) at ./malloc/malloc.c:4439 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 Title: gjs-console assert failure: free(): invalid pointer 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/gjs/+bug/1968440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967632] Re: apparmor denied when trying to load pkcs11 module for smart card authentication
** Changed in: firefox (Ubuntu) Importance: Undecided => High ** Changed in: firefox (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967632 Title: apparmor denied when trying to load pkcs11 module for smart card authentication Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968434] Re: Output Device shows only Dummy Output
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1968434 Title: Output Device shows only Dummy Output Status in alsa-driver package in Ubuntu: New Bug description: Audio was working yesterday. I turned on my computer today and the only output device is Dummy Output. Running aplay -l output is aplay: device_list:276: no soundcards found. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 12:04:59 2022 InstallationDate: Installed on 2021-05-24 (319 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2802 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2802:bd10/21/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-04-09T11:38:59.731560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1968434/+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 1968434] [NEW] Output Device shows only Dummy Output
You have been subscribed to a public bug: Audio was working yesterday. I turned on my computer today and the only output device is Dummy Output. Running aplay -l output is aplay: device_list:276: no soundcards found. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 12:04:59 2022 InstallationDate: Installed on 2021-05-24 (319 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2802 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2802:bd10/21/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-04-09T11:38:59.731560 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Output Device shows only Dummy Output https://bugs.launchpad.net/bugs/1968434 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
still seeing Apr 9 15:30:54 drafting-table /usr/libexec/gdm-x-session[355145]: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found in an install which is "jammy daily iso from a week or two back with daily dist upgrades", under i3; $ dpkg -l gdm3 x11-common i3-wm Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii gdm3 42.0-1ubuntu2 amd64GNOME Display Manager ii i3-wm 4.20.1-1amd64improved dynamic tiling window manager ii x11-common 1:7.7+23ubuntu2 all X Window System (X.Org) infrastructure -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1866454] Re: Intel NUC5CPYH - dual mouse pointer display when booting with two screens
Just tested on Ubuntu Mate 20.04.4 and - second mouse pointer still present on the right edge of the second screen, centered vertically (almost outside of screen just 2-3 pixel inside) as before, no change. - it looks like the artifacts on current mouse pointer no longer present, (not tested enough time, as artifacts does not appear always immediately) I do not use this system anymore for desktop use for more testing (is more like a mobile file server and occasional mobile desktop use) I will upgrade lo latest Ubuntu Mate and return with checking -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1866454 Title: Intel NUC5CPYH - dual mouse pointer display when booting with two screens Status in xf86-video-intel: New Status in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: Issue Description - - two mouse pointers on screen on booting with on dual monitor setup, One behave normally second is stuck just animate synchronously with first one. - The presence of second mouse pointer results in mouse pointer trailing artifacts and screen artifacts under mouse pointer, rendering desktop unusable. - On Ubuntu Mate the second mouse pointer appear on a screen edge, and on Regular Ubuntu it appear somewhere on one of the two screens. Affected Systems - Tested on Both Ubuntu Mate and regular Ubuntu, both version 19.10 and 20.04 Issue reproduction -- - booting with two monitors connected on affected system, (connecting second monitor after login screen -lightdm greeter ... - will prevent issue appear) Workarounds --- - booting with only one monitor connected, and connect the second one later after log-in screen appear. - on booting with two monitors on Ubuntu Mate: Disabling Marco - Adaptive compositor to "No Compositor" will solve pointer trailing and screen artifacts, (but the second mouse pointer remain outside screen. Note This system also has another mouse pointer bug https://bugs.launchpad.net/ubuntu-mate/+bug/1866452 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1866454/+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 1866452] Re: Intel NUC5CPYH - Mouse pointer display on HDMI out does not cover all screen
Just tested and the issue is still persistent on Ubuntu Mate 20.04.4 Not tested on latest Ubuntu Mate... I will give a try on latest live image, but if I remember correctly issue was no present in the past on the live image... I will also upgrade soon when I will have time -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1866452 Title: Intel NUC5CPYH - Mouse pointer display on HDMI out does not cover all screen Status in xf86-video-intel: New Status in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: Issue Description - Intel NUC5CPYH has two video outputs: - VGA - HDMI On HDMI Output - the visible pointer can't reach the left screen border by couple of pixels (it get stuck in a limit position) - the invisible pointer in the background handle normally. On VGA Out - the pointer both visible and invisible behave normally On Both Monitors connected on boot (Mate 20.04 beta) - the pointer both visible and invisible behave normally on both outputs - removing VGA monitor already logged in on desktop, mouse will behave also normally both visible and invisible on HDMI Output. Connect VGA monitor after boot (Mate 20.04 beta) - same issue as booting with HDMI out only - this does not matter if I use both screens after or just one, issue is related to boot initialization. It affects probably all Ubuntu distribution. Tested only on Ubuntu and Ubuntu Mate, both 19.10 and also 20.04 daily builds. Issue first noticed -- Issue first appear on Ubuntu Mate 16.04 after performing LTS hardware enabling Stack when first available, and find that is related to xserver-xorg HWE, by reverting it back, wile keeping HWE Kernel. Note This system also has another mouse pointer bug https://bugs.launchpad.net/ubuntu-mate/+bug/1866454 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1866452/+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 1968432] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate()
*** This bug is a duplicate of bug 1959937 *** https://bugs.launchpad.net/bugs/1959937 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1959937, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968432/+attachment/5578748/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1968432/+attachment/5578750/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1968432/+attachment/5578754/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1968432/+attachment/5578755/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1968432/+attachment/5578756/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1968432/+attachment/5578758/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968432/+attachment/5578759/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1959937 gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from process_ice_messages() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1968432 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate() Status in gnome-shell package in Ubuntu: New Bug description: The error message was generated immediately after login. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sat Apr 9 23:20:18 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-04-02 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220401) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7fb624cbe290 :cmpl $0x4,0x24(%rbx) PC (0x7fb624cbe290) ok source "$0x4" ok destination "0x24(%rbx)" (0xffb4) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_context_terminate () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate() 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/1968432/+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 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by
** Description changed: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to - return to the desktop, journal spits out js stacktrace and animations - become choppy. + return to the desktop, journal spits out js stacktrace. If you don't + trigger the crash then try opening and closing an app and trying again. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. -- 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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. If you don't trigger the crash then try opening and closing an app and trying again. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
Awesome, thanks a lot everyone!!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 Status in systemd package in Ubuntu: Fix Released Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1968390] Re: JS ERROR: TypeError: this.window_container is null
** Description changed: Ubuntu 22.04 Development - - A 3 finger touchpad swipe up/down gesture with 1 application open outputs a lot of JS errors and stacks to the journal. This issue may be the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 but the output is somewhat different when you have more than 1 app open. + A 3 finger touchpad swipe up/down gesture with 1 application open + outputs a lot of JS errors and stacks to the journal. This issue may be + the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome- + shell/+bug/1968383 but the output is somewhat different when you have + more than 1 app open. This also happens with all extensions disabled, does not happen in Fedora 36. To reproduce 1. login and open terminal and watch the journal 2. perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 3. See journal + 4. If nothing happens try opening an app, closing it and try again. Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Button (0x56219f5b8060), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:566 (4ce0bb0ac40 @ 10) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:567 (4ce0bb0ac40 @ 36) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:570 (4ce0bb0ac40 @ 77) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:638 (4ce0bb0ae20 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:353 (4ce0bb0a5b0 @ 62) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:357 (4ce0bb0a5b0 @ 87) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:364 (4ce0bb0a600 @ 8) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:160 (330c4e3cc560 @ 43) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a9a70 b resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #4 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08 21:18:49 x1c gnome-shell[21675]: #5 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Label (0x56219f5a8440), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a98b0 b resource:///org/gnome/shell/ui/environment.js:361 (330c4e3ccc90 @ 43) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:163 (330c4e3cc560 @ 91) Apr 08 21:18:49 x1c gnome-shell[2167
[Desktop-packages] [Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by
** Description changed: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to - return to the desktop, journal spits out js stacktrace. + return to the desktop, journal spits out js stacktrace and animations + become choppy. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. -- 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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace and animations become choppy. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+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 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator
For me Application in Terminal are continuing to run in the default MATE Terminal. I have latest Ubuntu MATE 22.04 LTS: ``` $ gsettings get org.mate.applications-terminal exec 'tilix' $ ls /etc/alternatives/x-terminal-emulator -al lrwxrwxrwx 1 root root 22 апр 9 19:01 /etc/alternatives/x-terminal-emulator -> /usr/bin/tilix.wrapper ``` Also please note that mate-desktop-environment is not installed on UM 22.04 LTS by default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1873750 Title: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator Status in brisk-menu package in Ubuntu: Invalid Status in classicmenu-indicator package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Confirmed Status in mate-desktop-environment package in Ubuntu: Fix Released Status in mate-menu package in Ubuntu: Invalid Status in mate-menus package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: Invalid Status in mate-settings-daemon package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: Fix Released Status in vala-panel-appmenu package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu MATE 20.04 LTS 2. Install non-default terminal - Tilix, by `sudo apt-get install tilix` 3. Install terminal-based application - Midnight Commander, by `sudo apt-get install mc` 3. Set Tilix as default terminal in `mate-default-applications-properties` or programmatically: gsettings set org.mate.applications-terminal exec "'tilix'" 4. Set Tilix as alternative for x-terminal-emulator by update- alternatives: update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper sudo update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper 5. Reboot 6. Add Custom Application Launcher to the MATE Panel: Type: Application in Terminal Name: mc Command: mc 7. Click the icon of just created Custom Application Launcher Expected results: * Midnight Commander is opened in the user-defined terminal - in Tilix Actual results: * Midnight Commander is default terminal - in MATE Terminal Notes: * This also happens with desktop-files installed by Midnight Commander, it opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, Dock, + menu, Advanced Mate Menu (`mate-menu` package) * What is interesting, the + respects user preferences and uses Tilix * Also ++ opens Tilix as expected. --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mate-panel 1.24.0-2 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: MATE Date: Mon Apr 20 10:48:51 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1873750/+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 1968428] [NEW] AMD HD7970 Error: no ums support in radeon modual
Public bug reported: System boots OK from USB install and shows the screen in 4k on my iiyama monitor. But after installation it just hangs with a cursor at the top left of the screen. So after editing grub with "nomodeset" it then boots with this error (no UMS support in Radeon module) then boots into the desktop at a fixed 1024x768.. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: User Name 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 16:27:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-30 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968428 Title: AMD HD7970 Error: no ums support in radeon modual Status in gnome-shell package in Ubuntu: New Bug description: System boots OK from USB install and shows the screen in 4k on my iiyama monitor. But after installation it just hangs with a cursor at the top left of the screen. So after editing grub with "nomodeset" it then boots with this error (no UMS support in Radeon module) then boots into the desktop at a fixed 1024x768.. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: User Name 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 16:27:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-30 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968428/+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 1810745] Re: HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 LTS and newer versions
Bug still exists in latest Ubuntu MATE 22.04 LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1810745 Title: HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 LTS and newer versions Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 18.04 LTS with all updates 2. Install HPLIP into it with `sudo apt install hplip-gui` 3. Log out. Expected results: * HPLIP shows hp-systray icon and its fully functional Actual results: * HPLIP shows hp-systrat icon but it is non-functional (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mate-panel 1.20.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jan 7 12:15:48 2019 InstallationDate: Installed on 2019-01-07 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1810745/+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 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color
The bug still exists in Ubuntu MATE 22.04 LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1721955 Title: Human, Human-Clearlooks and other themes have incorrect gray window title color Status in human-theme: New Status in community-themes package in Ubuntu: New Status in compiz package in Ubuntu: Confirmed Status in gtk+2.0 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in human-theme package in Ubuntu: Confirmed Status in marco package in Ubuntu: Invalid Status in mate-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE 2. Install Human theme from `human-theme` package 3. Select Human theme from `mate-control-center` Appearance Expected results: window title color is set to Ubuntu's orange (#FFBE6B) Actual results: window title color is set to different gray/silver color (#a5a5a2) Note: other themes are affected too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: human-theme 0.39.2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 15:43:03 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170925.1) PackageArchitecture: all SourcePackage: human-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/human-theme/+bug/1721955/+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 1968426] Re: gjs-console assert failure: free(): invalid pointer
*** This bug is a duplicate of bug 1946165 *** https://bugs.launchpad.net/bugs/1946165 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1946165, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968426/+attachment/5578708/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1968426/+attachment/5578710/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1968426/+attachment/5578714/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1968426/+attachment/5578715/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1968426/+attachment/5578716/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1968426/+attachment/5578717/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968426/+attachment/5578718/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1946165 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1968426 Title: gjs-console assert failure: free(): invalid pointer Status in gjs package in Ubuntu: New Bug description: I was working with gnome-extensions-app and the gnome-screenshot extension, and then this "report a bug" popup popped up. I'm not entirely sure what I did to cause this crash. I have seen this (or a similar) crash a few times before, but then it refused to send a report because I had pending updates (which are now installed). ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gjs 1.72.0-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AssertionMessage: free(): invalid pointer CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 16:55:36 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2022-04-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Extensions RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: gjs StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f11d1054b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f11d1052764 "free(): invalid pointer") at ./malloc/malloc.c:5664 _int_free (av=, p=, have_lock=0) at ./malloc/malloc.c:4439 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 Title: gjs-console assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev sambashare sudo wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1968426/+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 1967885] Re: blanking locks screen although screen lock is disabled
Running gsettings with sudo seems to nail it: sudo gsettings set org.gnome.desktop.lockdown disable-lock-screen 'true' But this disables screen locking for every user. That is irrelevant to me but some may care. -- 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/1967885 Title: blanking locks screen although screen lock is disabled Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I disabled screen lock from Settings > Privacy > Screen. Even so, I am forced to log in any time my screen has blanked. When I inspect dconf-editor (org.gnome.desktop.lockdown), I see that locking is indeed active. This looks like a discrepancy between the settings mechanism and dconf. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 16:06:06 2022 InstallationDate: Installed on 2022-03-27 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) 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/1967885/+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 1968425] Re: Workspace switching interruptible with trackpad overview gesture
** Description changed: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 gnome-shell: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status What happened: On the desktop when using a trackpad 3 finger swipe to - switch to an adjacent workspace if a 3 finger swipe up gesture to go to + switch to an adjacent workspace, if a 3 finger swipe up gesture to go to the activities overview is invoked during the transition animation it will abruptly cancel the transition and go to the overview at the original workspace. The abrupt cancellation can make the workspace/overview experience feel a bit jerky. What I expected: The transition to be non interruptible with the activities overview gesture only being able to used when the transition has concluded. This is the behaviour I observe when using workspaces on macOS. screen recording demonstrating this with libinput debug-gui to show trackpad gestures is attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 15:08:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968425 Title: Workspace switching interruptible with trackpad overview gesture Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 gnome-shell: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status What happened: On the desktop when using a trackpad 3 finger swipe to switch to an adjacent workspace, if a 3 finger swipe up gesture to go to the activities overview is invoked during the transition animation it will abruptly cancel the transition and go to the overview at the original workspace. The abrupt cancellation can make the workspace/overview experience feel a bit jerky. What I expected: The transition to be non interruptible with the activities overview gesture only being able to used when the transition has concluded. This is the behaviour I observe when using workspaces on macOS. screen recording demonstrating this with libinput debug-gui to show trackpad gestures is attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 15:08:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968425/+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 1968425] [NEW] Workspace switching interruptible with trackpad overview gesture
Public bug reported: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 gnome-shell: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status What happened: On the desktop when using a trackpad 3 finger swipe to switch to an adjacent workspace if a 3 finger swipe up gesture to go to the activities overview is invoked during the transition animation it will abruptly cancel the transition and go to the overview at the original workspace. The abrupt cancellation can make the workspace/overview experience feel a bit jerky. What I expected: The transition to be non interruptible with the activities overview gesture only being able to used when the transition has concluded. This is the behaviour I observe when using workspaces on macOS. screen recording demonstrating this with libinput debug-gui to show trackpad gestures is attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 15:08:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "screen recording demonstrating the bug" https://bugs.launchpad.net/bugs/1968425/+attachment/5578701/+files/workspace-switching-interrupt.webm ** Description changed: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 gnome-shell: - Installed: 42.0-1ubuntu1 - Candidate: 42.0-1ubuntu1 - Version table: - *** 42.0-1ubuntu1 500 - 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 42.0-1ubuntu1 + Candidate: 42.0-1ubuntu1 + Version table: + *** 42.0-1ubuntu1 500 + 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + 100 /var/lib/dpkg/status What happened: On the desktop when using a trackpad 3 finger swipe to switch to an adjacent workspace if a 3 finger swipe up gesture to go to the activities overview is invoked during the transition animation it will abruptly cancel the transition and go to the overview at the original workspace. The abrupt cancellation can make the workspace/overview experience feel a bit jerky. What I expected: The transition to be non interruptible with the activities overview gesture only being able to used when the transition has concluded. This is the behaviour I observe when using workspaces on macOS. - screen recording demonstrating this is attached + screen recording demonstrating this with libinput debug-gui to show + trackpad gestures is attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 15:08:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968425 Title: Workspace switching interruptible with trackpad overview gesture Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 gnome-shell: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status What happened: On the desktop when using a trackpad 3 finger swipe to switch to an adjacent workspace if a 3 finger swipe up gesture to go to the activities overview is invoked during the transition animation it will abruptly cancel the transition and go to the overview at the original workspace. The abrupt cancellation can make the workspace/overview experience feel a bit jerky. What I expected: The transition to be non interruptible wit
[Desktop-packages] [Bug 1968377] Re: New Chromium icon, not yet used by Snap
Looking at the snapcraft.yaml (https://git.launchpad.net/~chromium- team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml#n233) I think what needs to change is cp chrome/app/theme/chromium/product_logo_256.png $SNAPCRAFT_PART_INSTALL/chromium.png to cp chrome/app/theme/chromium/linux/product_logo_256.png $SNAPCRAFT_PART_INSTALL/chromium.png That is, add `linux` to the icon source path, since these new icons differ by platform. (If the code was on GitHub I'd submit a PR, but I'm very much a beginner with git and haven't done it on LP before.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1968377 Title: New Chromium icon, not yet used by Snap Status in chromium-browser package in Ubuntu: New Bug description: Google updated the Chrome/Chromium icons recently (see more at https://twitter.com/elvin_not_11/status/1489647032201465861), but I don't think the Snap icon has been updated. Here's the Chromium icons on the Chromium source GitHub mirror, which was easier for me to search: https://github.com/chromium/chromium/tree/main/chrome/app/theme/chromium/linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968377/+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 1958019]
I am assuming this is the same issue. My laptop is a Yoga 9 and I am able to get sound but it is very quite, not nearly as loud as in Windows. I have the pavucontrol cranked all the way up and its still super quite. Host: 82LU Yoga 9 14IAP7 Kernel: 5.17.1-arch1-1 I was under the understanding that upgrading to 5.17 would fix this but I guess not. Any help is appreciated -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to semaj4712 from comment #596) > I am assuming this is the same issue. My laptop is a Yoga 9 and I am able > to get sound but it is very quite, not nearly as loud as in Windows. I have > the pavucontrol cranked all the way up and its still super quite. > > Host: 82LU Yoga 9 14IAP7 > Kernel: 5.17.1-arch1-1 > > I was under the understanding that upgrading to 5.17 would fix this but I > guess not. Any help is appreciated Use aslamixer to increase max volume (command line tool). Some recent versions of pipewire tends to reset devices to very low levels and pavucontrol is not able to override the volume limiters. A couple of my systems required this method to fix sound volumes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1967885] Re: blanking locks screen although screen lock is disabled
-- 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/1967885 Title: blanking locks screen although screen lock is disabled Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I disabled screen lock from Settings > Privacy > Screen. Even so, I am forced to log in any time my screen has blanked. When I inspect dconf-editor (org.gnome.desktop.lockdown), I see that locking is indeed active. This looks like a discrepancy between the settings mechanism and dconf. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 16:06:06 2022 InstallationDate: Installed on 2022-03-27 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) 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/1967885/+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 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wpa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS Status in wpa package in Ubuntu: Confirmed Bug description: Using the current beta of Jammy, I no longer have stable WiFi after April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There is a chance it may also be related to network-manager going from 1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to wpasupplicant (see below) Wifi is stable often, but also often it fails to load webpages intermittently or fails to download the packages using apt for example, so it's not browser related. Example output of journalctl -xe -u wpasupplicant: Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1 Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with fc:34:97:23:4c:3c Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-94 txrate=27 Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=-95 txrate=27 Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying completed with fc:34:97:23:4c:3c [GTK=CCMP] Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-95 txrate=243000 Additional info: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy wpasupplicant wpasupplicant: Geïnstalleerd: 2:2.10-6 Kandidaat: 2:2.10-6 Versietabel: *** 2:2.10-6 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 8 21:28:12 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-03-12 (27 days ago) Insta
[Desktop-packages] [Bug 1832414] Re: Removing document files spam from cups
Today 2022-04-09, I also saw this on my Rocky Linux (updated) after a reboot after a crash, but "systemctl stop cups" and then "systemctl start cups" as root, resolved the issue. Sorry I have no more info than that. ; cups-2.2.6-40.el8.x86_64, Linux 4.18.0-348.12.2.el8_5.x86_64 #1 SMP Wed Jan 19 17:53:40 UTC 2022 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1832414 Title: Removing document files spam from cups Status in cups package in Ubuntu: Confirmed Bug description: Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last night the CUPS logs have had a considerable number of messages from cupsd stating "Removing document files" - about 3 or 4 a second constantly. Stopping the cups service stops the log-spam, and starting it again immediately resumes it (after a few hundred "Loading from cache..." messages). I've tried removing document files from the cache (there were a couple of ancient ones lying around - it's not a heavily used printer), but this made little difference to the symptoms. I'm pretty confident this is due to the upgrade as: 1. the spam in the logs starts immediately after CUPS reloads (after the upgrade) 2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and cupsdCleanJobs in scheduler/job.c) If I can provide any further information, do let me know! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1832414/+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 1967245] Re: 'net usershare' returned error 255 on jammy-desktop-amd64
Ok, that's a different issue, and a configuration one. You have to check the file permissions on /home, /home/vm and /home/vm/share and make sure the user guest is mapped to on the server can access those directories and the files in it. To find out which linux user on the server that is, check the "map to guest" and "guest account" parameters in smb.conf. I will close this bug since the original issue, "net usershare", is now working. If you think there is still a problem with samba, please file a new bug for that specific issue describing the behavior. Thanks for filing this bug, though, it was a real issue that we were able to fix because of this report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1967245 Title: 'net usershare' returned error 255 on jammy-desktop-amd64 Status in nautilus-share package in Ubuntu: Fix Released Bug description: jammy-desktop-amd64.iso 2022-03-26 08:25 'net usershare' returned error 255: net usershare add: cannot convert name "Everyone" to a SID. Access denied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1967245/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
This bug was fixed in the package systemd - 249.11-0ubuntu3 --- systemd (249.11-0ubuntu3) jammy; urgency=medium * oomd: calculate 'used' memory with MemAvailable instead of MemFree (LP: #1966381) File: debian/patches/lp1966381-oomd-calculate-used-memory-with-MemAvailable-instead-of-M.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15fc4c53d726e1dcae7296a9306cfd453fd1a046 * hwdb: remove the tablet pad entry for the UC-Logic 1060N (LP: #1926860) File: debian/patches/lp1926860-hwdb-remove-the-tablet-pad-entry-for-the-UC-Logic-1060N.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7bf31946a52e55f9f6ea4ecfa30e311685b20997 -- Nick Rosbrook Thu, 07 Apr 2022 15:28:15 -0400 ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 Status in systemd package in Ubuntu: Fix Released Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1968412] [NEW] When trying to open the program it says that i need to be in a special group to use it
Public bug reported: Version: 0.99.22 Kubuntu version 22.04 I expected it to open up the software properties without any errors. It said that i need to be in a special group (wheel) to use it. It says the password is incorrect even though i use this password to log in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.22 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Apr 9 11:59:59 2022 InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) 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 jammy -- 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/1968412 Title: When trying to open the program it says that i need to be in a special group to use it Status in software-properties package in Ubuntu: New Bug description: Version: 0.99.22 Kubuntu version 22.04 I expected it to open up the software properties without any errors. It said that i need to be in a special group (wheel) to use it. It says the password is incorrect even though i use this password to log in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.22 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Apr 9 11:59:59 2022 InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) 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/1968412/+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 1968407] Re: gnome-calendar crashed with SIGSEGV in g_source_get_ready_time()
*** This bug is a duplicate of bug 1869068 *** https://bugs.launchpad.net/bugs/1869068 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1869068, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968407/+attachment/5578562/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1968407/+attachment/5578564/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1968407/+attachment/5578568/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1968407/+attachment/5578569/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1968407/+attachment/5578570/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1968407/+attachment/5578571/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968407/+attachment/5578572/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1869068 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1968407 Title: gnome-calendar crashed with SIGSEGV in g_source_get_ready_time() Status in gnome-calendar package in Ubuntu: New Bug description: An error has occurred the closing application.. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-calendar 41.2-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 10:41:38 2022 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220408) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7f585f070fb8 : mov 0x10(%rax),%rax PC (0x7f585f070fb8) ok source "0x10(%rax)" (0x0010) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_source_get_ready_time () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () 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 Title: gnome-calendar crashed with SIGSEGV in g_source_get_ready_time() 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-calendar/+bug/1968407/+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 1968405] [NEW] File missing in package?
Public bug reported: The upgrade from Ubuntu 21.10 to 22.04 - Ubuntu Jammy Jellyfish (development branch) - stopped. An "apt install -f" shows that a file is missing in the Yaru package: - root@besa:/home/daniele/Downloads# apt install -f Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze... Fatto Lettura informazioni sullo stato... Fatto Correzione delle dipendenze... Fatto I seguenti pacchetti aggiuntivi saranno inoltre installati: yaru-theme-gnome-shell I seguenti pacchetti saranno aggiornati: yaru-theme-gnome-shell 1 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati. 4 non completamente installati o rimossi. È necessario scaricare 0 B/85,4 kB di archivi. Dopo quest'operazione, verranno occupati 14,9 MB di spazio su disco. Continuare? [Y/n] (Lettura del database... 392424 file e directory attualmente installati.) Preparativi per estrarre .../yaru-theme-gnome-shell_22.04.3.1_all.deb... Estrazione di yaru-theme-gnome-shell (22.04.3.1) su (21.10.2)... dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/yaru-theme-gnome-shell_22.04.3.1_all.deb (--unpack): impossibile aprire "/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such file or directory Segnalazione apport non scritta poiché il messaggio di errore indica un errore nel sistema locale. Si sono verificati degli errori nell'elaborazione: /var/cache/apt/archives/yaru-theme-gnome-shell_22.04.3.1_all.deb The error line is: "/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such file or directory I unpacked the deb file and indeed there's no calendar-today- light.svg.dpkg-new file, the right name is calendar-today-light.svg It looks like a bug. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1968405 Title: File missing in package? Status in yaru-theme package in Ubuntu: New Bug description: The upgrade from Ubuntu 21.10 to 22.04 - Ubuntu Jammy Jellyfish (development branch) - stopped. An "apt install -f" shows that a file is missing in the Yaru package: - root@besa:/home/daniele/Downloads# apt install -f Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze... Fatto Lettura informazioni sullo stato... Fatto Correzione delle dipendenze... Fatto I seguenti pacchetti aggiuntivi saranno inoltre installati: yaru-theme-gnome-shell I seguenti pacchetti saranno aggiornati: yaru-theme-gnome-shell 1 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati. 4 non completamente installati o rimossi. È necessario scaricare 0 B/85,4 kB di archivi. Dopo quest'operazione, verranno occupati 14,9 MB di spazio su disco. Continuare? [Y/n] (Lettura del database... 392424 file e directory attualmente installati.) Preparativi per estrarre .../yaru-theme-gnome-shell_22.04.3.1_all.deb... Estrazione di yaru-theme-gnome-shell (22.04.3.1) su (21.10.2)... dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/yaru-theme-gnome-shell_22.04.3.1_all.deb (--unpack): impossibile aprire "/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such file or directory Segnalazione apport non scritta poiché il messaggio di errore indica un errore nel sistema locale. Si sono verificati degli errori nell'elaborazione: /var/cache/apt/archives/yaru-theme-gnome-shell_22.04.3.1_all.deb The error line is: "/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such file or directory I unpacked the deb file and indeed there's no calendar-today- light.svg.dpkg-new file, the right name is calendar-today-light.svg It looks like a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1968405/+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 1967245] Re: 'net usershare' returned error 255 on jammy-desktop-amd64
'net usershare' returned error 255: this works ok. guest can not visit the share path /home/vm/share, but able to visit /var/samba. the same /etc/samba/smb.conf works on ubuntu21,20,18,16. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1967245 Title: 'net usershare' returned error 255 on jammy-desktop-amd64 Status in nautilus-share package in Ubuntu: Fix Released Bug description: jammy-desktop-amd64.iso 2022-03-26 08:25 'net usershare' returned error 255: net usershare add: cannot convert name "Everyone" to a SID. Access denied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1967245/+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 1967245] Re: 'net usershare' returned error 255 on jammy-desktop-amd64
** Attachment removed: "_16494866354113.png" https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1967245/+attachment/5578529/+files/%E4%BC%81%E4%B8%9A%E5%BE%AE%E4%BF%A1%E6%88%AA%E5%9B%BE_16494866354113.png ** Attachment added: "20220409145644.jpg" https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1967245/+attachment/5578530/+files/20220409145644.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1967245 Title: 'net usershare' returned error 255 on jammy-desktop-amd64 Status in nautilus-share package in Ubuntu: Fix Released Bug description: jammy-desktop-amd64.iso 2022-03-26 08:25 'net usershare' returned error 255: net usershare add: cannot convert name "Everyone" to a SID. Access denied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1967245/+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
