[Desktop-packages] [Bug 1965656] [NEW] gnome shell overuses memory causing overheating
Public bug reported: My laptop with an i7 10750H CPU and NVIDIA 2070 MaxQ GPU undergoes overheating often. I checked the CPU usage and it is gnome-shell over using the memory. it seems to use about 1.5GB of RAM, which is very suspicious. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.7 ProcVersionSignature: Ubuntu 5.4.0-104.118~18.04.1-generic 5.4.166 Uname: Linux 5.4.0-104-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 01:28:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-14 (33 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1965656 Title: gnome shell overuses memory causing overheating Status in gnome-shell package in Ubuntu: New Bug description: My laptop with an i7 10750H CPU and NVIDIA 2070 MaxQ GPU undergoes overheating often. I checked the CPU usage and it is gnome-shell over using the memory. it seems to use about 1.5GB of RAM, which is very suspicious. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.7 ProcVersionSignature: Ubuntu 5.4.0-104.118~18.04.1-generic 5.4.166 Uname: Linux 5.4.0-104-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 01:28:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-14 (33 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) 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/1965656/+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 1936935] Re: Black characters on dark grey background in dark mode
This bug was fixed in the package gnome-characters - 41.0-4 --- gnome-characters (41.0-4) unstable; urgency=medium * Cherry-pick improved dark theme patch (LP: #1936935) -- Jeremy Bicha Sat, 19 Mar 2022 13:33:25 -0400 ** Changed in: gnome-characters (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1936935 Title: Black characters on dark grey background in dark mode Status in GNOME Characters: Unknown Status in gnome-characters package in Ubuntu: Fix Released Bug description: Ubuntu 21.04 gnome-characters 40.0-1 Expected behaviour: display white characters on a dark grey background when using Dark as the selected Window colour. Observed behaviour: characters are displayed in black on a dark grey background when using Dark as the selected Window colour. I would be very grateful indeed if this issue could be addressed. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-characters/+bug/1936935/+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 1965189] Re: Add session migration for GNOME 42 dark theme
This bug was fixed in the package gsettings-desktop-schemas - 42~rc-1ubuntu3 --- gsettings-desktop-schemas (42~rc-1ubuntu3) jammy; urgency=medium * Add dark-theme migration script using dh-migrations (LP: #1965189) -- Jeremy Bicha Thu, 17 Mar 2022 09:49:43 -0400 ** Changed in: gsettings-desktop-schemas (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1965189 Title: Add session migration for GNOME 42 dark theme Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Status in gsettings-desktop-schemas source package in Jammy: Fix Released Bug description: Test Case - 1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance and choose Dark 2. Upgrade to Ubuntu 22.04 LTS 3. Log out then log back in 4. Your apps should still be dark Linked Issue That test case is broken by the libhandy update. See LP: #1964841 We are updating gnome-control-center to set the correct gsettings value (below) when choosing a dark theme. Workaround -- If you want the fix to apply without logging out at any time, you can run session-migration --file /usr/share/session-migration/scripts/dark-theme-migration.sh This requires gsettings-desktop-schemas 42~rc-1ubuntu3 or higher Or you can run this command yourself instead gsettings set org.gnome.desktop.interface color-scheme 'prefer-dark' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1965189/+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 1965647] Re: pulseaudio gets stuck after launching firefox
seems like pulse was fighting with pipewire; not sure what I did to clean it up but appears to be working better now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1965647 Title: pulseaudio gets stuck after launching firefox Status in pulseaudio package in Ubuntu: New Bug description: after updating to jammy, pulseaudio appears to get stuck after opening firefox. I can play an audio file using mplayer fine, then I open firefox (either snap or deb version), then it fails to play the same audio file and prints out "Audio device got stuck!" killing pulseaudio (and having systemd user session restart it) restores sound in mplayer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 3283 F wireplumber /dev/snd/controlC0: jbarnett 3283 F wireplumber jbarnett 7684 F pulseaudio /dev/snd/seq:jbarnett 3278 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:29:11 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1965647/+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 1965639] Re: purple screen after login using fingerprint
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1965639 Title: purple screen after login using fingerprint Status in xorg package in Ubuntu: New Bug description: I updated the machine yesterday, and additionally added the fingerprint to pam using pam-auth-update. The screen now stays purple after logging in using the finger, but works fine after logging in using the password. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 21:37:43 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.13.0-28-generic, x86_64: installed nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2294] InstallationDate: Installed on 2020-12-10 (464 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20NN002NGE ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=2bcb2bd8-2364-4f28-9085-f6c366d45c6d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2021 dmi.bios.release: 1.89 dmi.bios.vendor: LENOVO dmi.bios.version: N2LET89W (1.89 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NN002NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN2LET89W(1.89):bd11/24/2021:br1.89:efr1.20:svnLENOVO:pn20NN002NGE:pvrThinkPadX390Yoga:rvnLENOVO:rn20NN002NGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20NN_BU_Think_FM_ThinkPadX390Yoga: dmi.product.family: ThinkPad X390 Yoga dmi.product.name: 20NN002NGE dmi.product.sku: LENOVO_MT_20NN_BU_Think_FM_ThinkPad X390 Yoga dmi.product.version: ThinkPad X390 Yoga dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1965639/+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 1965639] [NEW] purple screen after login using fingerprint
You have been subscribed to a public bug: I updated the machine yesterday, and additionally added the fingerprint to pam using pam-auth-update. The screen now stays purple after logging in using the finger, but works fine after logging in using the password. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 21:37:43 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.13.0-28-generic, x86_64: installed nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2294] InstallationDate: Installed on 2020-12-10 (464 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20NN002NGE ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=2bcb2bd8-2364-4f28-9085-f6c366d45c6d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2021 dmi.bios.release: 1.89 dmi.bios.vendor: LENOVO dmi.bios.version: N2LET89W (1.89 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NN002NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN2LET89W(1.89):bd11/24/2021:br1.89:efr1.20:svnLENOVO:pn20NN002NGE:pvrThinkPadX390Yoga:rvnLENOVO:rn20NN002NGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20NN_BU_Think_FM_ThinkPadX390Yoga: dmi.product.family: ThinkPad X390 Yoga dmi.product.name: 20NN002NGE dmi.product.sku: LENOVO_MT_20NN_BU_Think_FM_ThinkPad X390 Yoga dmi.product.version: ThinkPad X390 Yoga dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- purple screen after login using fingerprint https://bugs.launchpad.net/bugs/1965639 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965649] [NEW] package yaru-theme-icon 22.04.2 failed to install/upgrade: trying to overwrite '/usr/share/icons/Yaru/16x16/panel/a11y.svg', which is also in package yaru-theme-
Public bug reported: I was in the process of updating Ubuntu Unity 22.04 and got thrown this error. Was not doing anything on laptop except updating. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: yaru-theme-icon 22.04.2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 19 18:26:45 2022 Dependencies: ErrorMessage: trying to overwrite '/usr/share/icons/Yaru/16x16/panel/a11y.svg', which is also in package yaru-theme-unity 21.10.2 InstallationDate: Installed on 2022-03-19 (0 days ago) InstallationMedia: Ubuntu Unity 22.04 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu1 apt 2.4.1 SourcePackage: yaru-theme Title: package yaru-theme-icon 22.04.2 failed to install/upgrade: trying to overwrite '/usr/share/icons/Yaru/16x16/panel/a11y.svg', which is also in package yaru-theme-unity 21.10.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/1965649 Title: package yaru-theme-icon 22.04.2 failed to install/upgrade: trying to overwrite '/usr/share/icons/Yaru/16x16/panel/a11y.svg', which is also in package yaru-theme-unity 21.10.2 Status in yaru-theme package in Ubuntu: New Bug description: I was in the process of updating Ubuntu Unity 22.04 and got thrown this error. Was not doing anything on laptop except updating. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: yaru-theme-icon 22.04.2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 19 18:26:45 2022 Dependencies: ErrorMessage: trying to overwrite '/usr/share/icons/Yaru/16x16/panel/a11y.svg', which is also in package yaru-theme-unity 21.10.2 InstallationDate: Installed on 2022-03-19 (0 days ago) InstallationMedia: Ubuntu Unity 22.04 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu1 apt 2.4.1 SourcePackage: yaru-theme Title: package yaru-theme-icon 22.04.2 failed to install/upgrade: trying to overwrite '/usr/share/icons/Yaru/16x16/panel/a11y.svg', which is also in package yaru-theme-unity 21.10.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1965649/+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 1965648] [NEW] Autorotate initiates, but doesn't reset
Public bug reported:
In jammy I can get mutter's auto-rotate to switch to portrait mode
("right-up") by rotating the device (this only worked in impish if I
installed the autorotate gnome-shell extension).
However, putting it back into "normal" orientation doesn't put the
screen back in landscape mode. Flipping it around ("left-up") does swap
to the reverse portrait mode, but still can't get back to "normal"
afterward.
running `monitor-sensor` does show the accelerometer orientation change
events (including the "normal" ones) triggering properly, just the
desktop doesn't respond.
Plugging in an external monitor does seem to trigger the desktop to go
back to normal landscape mode.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter 42~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Mar 19 15:41:42 2022
InstallationDate: Installed on 2019-08-17 (945 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: mutter
UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1965648
Title:
Autorotate initiates, but doesn't reset
Status in mutter package in Ubuntu:
New
Bug description:
In jammy I can get mutter's auto-rotate to switch to portrait mode
("right-up") by rotating the device (this only worked in impish if I
installed the autorotate gnome-shell extension).
However, putting it back into "normal" orientation doesn't put the
screen back in landscape mode. Flipping it around ("left-up") does
swap to the reverse portrait mode, but still can't get back to
"normal" afterward.
running `monitor-sensor` does show the accelerometer orientation
change events (including the "normal" ones) triggering properly, just
the desktop doesn't respond.
Plugging in an external monitor does seem to trigger the desktop to go
back to normal landscape mode.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter 42~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Mar 19 15:41:42 2022
InstallationDate: Installed on 2019-08-17 (945 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: mutter
UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+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 1965646] [NEW] pulseaudio missing even though says installed in software center. Have no audio
Public bug reported: Previously: had SoundHissheadphones https://answers.launchpad.net/ubuntu/+question/700984 Messed with pulseaudio until it's totally gone even though on the software center it still says it is installed but unable to remove it because it says: "PulseAudio System Tray": no packages to remove Sudo apt remove pulseaudio Removing pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Setting up pipewire-pulse (0.3.48-1ubuntu1) ... Created symlink /etc/systemd/user/default.target.wants/pipewire-pulse.service → /usr/lib/systemd/user/pipewire-pulse.service. Created symlink /etc/systemd/user/sockets.target.wants/pipewire-pulse.socket → / usr/lib/systemd/user/pipewire-pulse.socket. Processing triggers for man-db (2.10.1-1) ... Processing triggers for libglib2.0-0:amd64 (2.71.3-1) ... sudo apt purge Purging configuration files for pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Processing triggers for dbus (1.12.20-2ubuntu3) . ___ No audio symbol, it's gone Software center still says it is installed. Unable to remove "PulseAudio" in software center Unable to remove"PulseAudio Volume Control": no packages to remove Version 0.17.0 ___ mate-volume-control No device to configure under Hardware Input: unchecked Monitor of Dummy Output Output: unchecked Dummy Output Stereo __ sudo apt-get update -y sudo apt-get install -y pulseaudio Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libsbc1 libssl1.1 linux-headers-5.13.0-19 Use 'sudo apt autoremove' to remove them. Suggested packages: pavumeter paprefs ubuntu-sounds The following NEW packages will be installed: pulseaudio 0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded. Need to get 0 B/913 kB of archives. After this operation, 4,674 kB of additional disk space will be used. Selecting previously unselected package pulseaudio. (Reading database ... 321785 files and directories currently installed.) Preparing to unpack .../pulseaudio_1%3a15.99.1+dfsg1-1ubuntu1_amd64.deb ... Unpacking pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Setting up pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Adding user pulse to group audio Created symlink /etc/systemd/user/default.target.wants/pulseaudio.service → /usr/lib/systemd/user/pulseaudio.service. Created symlink /etc/systemd/user/sockets.target.wants/pulseaudio.socket → /usr/lib/systemd/user/pulseaudio.socket. Processing triggers for man-db (2.10.1-1) ... Processing triggers for dbus (1.12.20-2ubuntu3) ...y sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libsbc1 libssl1.1 linux-headers-5.13.0-19 0 upgraded, 0 newly installed, 3 to remove and 7 not upgraded. After this operation, 80.1 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 321976 files and directories currently installed.) Removing libsbc1:amd64 (1.5-3build1) ... Removing libssl1.1:amd64 (1.1.1l-1ubuntu1) ... Removing linux-headers-5.13.0-19 (5.13.0-19.19) ... Processing triggers for libc-bin (2.35-0ubuntu3) ... pulseaudio W: [pulseaudio] pid.c: Stale PID file, overwriting. E: [pulseaudio] socket-server.c: bind(): Address already in use E: [pulseaudio] module.c: Failed to load module "module-native-protocol-unix" (argument: ""): initialization failed. E: [pulseaudio] main.c: D-Bus name org.pulseaudio.Server already taken. pulseaudio -k E: [pulseaudio] main.c: Failed to kill daemon: No such process __ ubuntu-bug -s audio Package pulseaudio 1:15:99.1+dgsg1-1ubuntu1 2.20.11-Outbuntu79 __ killall pulseaudio; pulseaudio -k ; rm -r ~/.config/pulse/* ; rm -r ~/.pulse* rm -r ~/.pulse* pulseaudio: no process found E: [pulseaudio] main.c: Failed to kill daemon: No such process rm: cannot remove '/home/ptosis/.pulse*': No such file or directory pulseaudio --start waited 10 seconds, then reboot wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x ./alsa-info.sh && ./alsa-info.sh bash alsa-info.sh --stdout AFTER REBOOT: wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x ./alsa-info.sh && ./alsa-info.sh --2022-03-19 07:09:23-- http://www.alsa-project.org/alsa-info.sh Resolving www.alsa-project.org (www.alsa-project.org)... 207.180.221.201 Connecting to www.alsa-project.org (www.alsa-project.org)|207.180.221.201|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://www.alsa-project.org/alsa-info.sh [following] --2022-03-19 07:09:24-- https://www.alsa-project.org/alsa-info.sh Connecting to www.alsa-project.org (www.alsa-project.org)|207.180.221.201|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location:
[Desktop-packages] [Bug 1965647] [NEW] pulseaudio gets stuck after launching firefox
Public bug reported: after updating to jammy, pulseaudio appears to get stuck after opening firefox. I can play an audio file using mplayer fine, then I open firefox (either snap or deb version), then it fails to play the same audio file and prints out "Audio device got stuck!" killing pulseaudio (and having systemd user session restart it) restores sound in mplayer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 3283 F wireplumber /dev/snd/controlC0: jbarnett 3283 F wireplumber jbarnett 7684 F pulseaudio /dev/snd/seq:jbarnett 3278 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:29:11 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: after updating to jammy, pulseaudio appears to get stuck after opening firefox. - I can play an audio file using mplayer fine, then I open firefox, then it fails to play the same audio file and prints out + I can play an audio file using mplayer fine, then I open firefox (either snap or deb version), then it fails to play the same audio file and prints out "Audio device got stuck!" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: jbarnett 3283 F wireplumber - /dev/snd/controlC0: jbarnett 3283 F wireplumber - jbarnett 7684 F pulseaudio - /dev/snd/seq:jbarnett 3278 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC1: jbarnett 3283 F wireplumber + /dev/snd/controlC0: jbarnett 3283 F wireplumber + jbarnett 7684 F pulseaudio + /dev/snd/seq:jbarnett 3278 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:29:11 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Description changed: after updating to jammy, pulseaudio appears to get stuck after opening firefox. - I can play an audio file using mplayer fine, then I open firefox (either snap or deb version), then it fails to play the same audio file and prints out + I can play an audio file using mplayer fine, then I open firefox, then it fails to play the same audio file and prints out "Audio device got stuck!" + + killing pulseaudio (and having systemd user session restart it) restores + sound in mplayer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 3283 F wireplumber /dev/snd/controlC0: jbarnett 3283 F wireplumber jbarnett 7684 F pulseaudio /dev/snd/seq:jbarnett 3278 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:29:11 2022 InstallationDate:
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
** Changed in: firefox Status: Confirmed => In Progress -- 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 1965642] [NEW] appearance selection will break the UI
Public bug reported: as soon as you click the appearance option, the sidebar will disappear (forever) and you cannot, after closing settings (gnome control center), re-open it in any way. only solution i found is to reset all options via terminal: dconf reset -f / ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 22:29:12 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-19 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1965642 Title: appearance selection will break the UI Status in gnome-control-center package in Ubuntu: New Bug description: as soon as you click the appearance option, the sidebar will disappear (forever) and you cannot, after closing settings (gnome control center), re-open it in any way. only solution i found is to reset all options via terminal: dconf reset -f / ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 22:29:12 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-19 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash 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/1965642/+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 1965638] [NEW] Can't drag to reorder tabs
Public bug reported: After upgrading from impish to jammy, seeing the following behavior in firefox when trying to reorder tabs by clicking and dragging them: 1) in the .deb firefox, firefox will crash most of the time, but sometimes reorder successfully 2) in the snap firefox, firefox will not register the drag (nothing will happen). Following attempting to drag the tab, the next click in firefox is discarded/ignored and things like mouse wheel scrolls don't work until firefox is clicked in ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 97.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 92319 F pulseaudio BuildID: 20220216172458 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Sat Mar 19 13:37:18 2022 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.6.86 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=98.0.1/20220313140707 (Out of date) RunningIncompatibleAddons: False Snap.Changes: ID Status Spawn Ready Summary 495 Done2022-03-19T13:27:26-07:00 2022-03-19T13:30:56-07:00 Remove "firefox" snap 496 Done2022-03-19T13:33:19-07:00 2022-03-19T13:34:07-07:00 Install "firefox" snap SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to jammy on 2022-03-18 (0 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1965638 Title: Can't drag to reorder tabs Status in firefox package in Ubuntu: New Bug description: After upgrading from impish to jammy, seeing the following behavior in firefox when trying to reorder tabs by clicking and dragging them: 1) in the .deb firefox, firefox will crash most of the time, but sometimes reorder successfully 2) in the snap firefox, firefox will not register the drag (nothing will happen). Following attempting to drag the tab, the next click in firefox is discarded/ignored and things like mouse wheel scrolls don't work until firefox is clicked in ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 97.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 92319 F pulseaudio BuildID: 20220216172458 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Sat Mar 19 13:37:18 2022 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000
[Desktop-packages] [Bug 1965609] Re: Several Hungarian keyboard layout labels untranslated
(Possibly it's a bug in the gnome-desktop package. But let's report it to gnome-control-center, and have upstream sort it.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1965609 Title: Several Hungarian keyboard layout labels untranslated Status in gnome-control-center package in Ubuntu: Confirmed Status in xkeyboard-config package in Ubuntu: Invalid Bug description: Wen I wanted to choose a Hungarian layout, I saw, that not all Hungarian layouts' name translated into Hungarian language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965609/+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 1965609] Re: Not all Hunngarian keyboard layouts' name translated to Hungarian layout
Thanks for your report. In xkeyboard-config the string representing the first of those layout variants looks like this: "Hungarian (101/QWERTY/comma/dead keys)" And that string has a Hungarian translation: https://translations.launchpad.net/ubuntu/jammy/+source/xkeyboard- config/+pots/xkeyboard-config/hu/515 However, the gnome-control-center developers seem to think that commas look better than slashes to separate the various aspects of the layout: "Hungarian (QWERTY, 101-key, comma, dead keys)" But by splitting and recreating the string that way, they end up with a different string for which no translation exists. And that's most likely the explanation for the other untranslated layout names as well. And it's not only affecting users with a Hungarian locale — I see those strings untranslated when using a Swedish locale, for instance. So it's a bug in gnome-control-center. @Viktor: It would be great if you could call upstream's attention to this by submitting an issue: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues If you do, can you please post the URL to the upstream issue here for tracking purposes. ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed ** Changed in: xkeyboard-config (Ubuntu) Status: New => Invalid ** Summary changed: - Not all Hunngarian keyboard layouts' name translated to Hungarian layout + Several Hungarian keyboard layout labels untranslated -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1965609 Title: Several Hungarian keyboard layout labels untranslated Status in gnome-control-center package in Ubuntu: Confirmed Status in xkeyboard-config package in Ubuntu: Invalid Bug description: Wen I wanted to choose a Hungarian layout, I saw, that not all Hungarian layouts' name translated into Hungarian language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965609/+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 1965610] Re: Extra layouts don't work on Hungarian UI
You should run that command without "sudo". gsettings set org.gnome.desktop.input-sources show-all-sources true ** Package changed: xkeyboard-config (Ubuntu) => gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1965610 Title: Extra layouts don't work on Hungarian UI Status in gnome-control-center package in Ubuntu: Invalid Bug description: When I set into a terminal the following command: "sudo gsettings set org.gnome.desktop.input-sources show-all-sources true" it fails. We required for "Old Hungarian" layout, short description:"oldhun" -> "Székely-magyar rovásírás" and "Old Hungarian (for ligatures)" layout, short description: "oldhun(lig)" id:"oldhunlig" ->"Székely-magyar rovásírás (ligatúrákhoz)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965610/+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 1965635] Re: Crash on close file chooser (Chrome)
*** This bug is a duplicate of bug 1956801 *** https://bugs.launchpad.net/bugs/1956801 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 #1956801, 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/1965635/+attachment/5570824/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1965635/+attachment/5570826/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1965635/+attachment/5570830/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1965635/+attachment/5570831/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1965635/+attachment/5570832/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1965635/+attachment/5570833/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1965635/+attachment/5570834/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1956801 xdg-desktop-portal-gtk crashed with SIGSEGV in gdk_window_set_transient_for() ** 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 xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1965635 Title: Crash on close file chooser (Chrome) Status in xdg-desktop-portal-gtk package in Ubuntu: New Bug description: Crash on close (click cancel) file chooser (open file) (Chrome) ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal-gtk 1.12.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-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 19:54:14 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk InstallationDate: Installed on 2022-03-11 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310) ProcCmdline: /usr/libexec/xdg-desktop-portal-gtk SegvAnalysis: Segfault happened at: 0x7fb3f7d79e94 : mov0x18(%rdi),%rax PC (0x7fb3f7d79e94) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: xdg-desktop-portal-gtk StacktraceTop: gdk_window_set_transient_for () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_popover_set_relative_to () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: xdg-desktop-portal-gtk crashed with SIGSEGV in gdk_window_set_transient_for() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo www-data separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1965635/+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 1664369] Re: Super key always applied for VNC session
Is this still problem in 20.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1664369 Title: Super key always applied for VNC session Status in metacity package in Ubuntu: New Bug description: This a regression report for bug 1440570 with the latest package installed on 14.04 Trusty. Problem still reproduces exactly as specified. Every time I press 'N' in terminal over VNC, a new window is opened. I don't want to delete my super key mappings, they are quite useful when interacting with the machine locally but I also need remote access to things like a web browser and VNC is most useful for this. Unfortunately the super key is constantly on. I saw that 1440570 was closed with a fix, I might have undone the fix because I used gnome- tweak-tool to swap my Alt-Win keys (Alt-Win behavior under typing). Even after switching this back however, the problem persists over VNC, making it unusable. Let me know what I can do to help debug. Output of apt list metacity: Listing... Done metacity/trusty-updates,now 1:2.34.13-0ubuntu4.1 amd64 [installed] Output of lsb_release -rd: Description:Ubuntu 14.04.5 LTS Release:14.04 #regression-update ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Feb 13 11:40:39 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-xenial, 0.201611160201~ubuntu14.04.1, 4.4.0-62-generic, x86_64: installed synaptic-i2c-hid-3.13.0-32-backport, 1.6.4: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06b9] InstallationDate: Installed on 2016-12-16 (59 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 MachineType: Dell Inc. OptiPlex 7040 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=e4b640d9-85ce-43f1-9369-2744897fd9f5 ro pcie_aspm=off quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.9 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.9:bd09/12/2016:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 7040 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 8 15:18:04 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16485 vendor DEL xserver.version: 2:1.18.3-1ubuntu2.3~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1664369/+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 1965627] [NEW] Returning from suspend login screen password barely visible
Public bug reported: Returning from suspend login screen password field barely visible. see attachment. corrado@corrado-p5-jj-0203:~$ inxi -Fx System: Host: corrado-p5-jj-0203 Kernel: 5.15.0-23-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 42.beta Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Desktop Mobo: Gigabyte model: H87M-D3H v: x.x serial: UEFI: American Megatrends v: F3 date: 04/24/2013 CPU: Info: dual core model: Intel Core i3-4130 bits: 64 type: MT MCP arch: Haswell rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 2195 high: 2196 min/max: 800/3400 cores: 1: 2195 2: 2195 3: 2195 4: 2196 bogomips: 27136 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel 4th Generation Core Processor Family Integrated Graphics vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0 Display: wayland server: X.Org v: 1.22.1 with: Xwayland v: 22.1.0 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1680x1050~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 21.3.5 direct render: Yes Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel v: kernel bus-ID: 00:03.0 Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 Sound Server-1: ALSA v: k5.15.0-23-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: kernel port: e000 bus-ID: 02:00.0 IF: enp2s0 state: down mac: 94:de:80:7e:90:a7 Device-2: D-Link DWA-121 802.11n Wireless N 150 Pico Adapter [Realtek RTL8188CUS] type: USB driver: rtl8192cu bus-ID: 3-14:5 IF: wlx48ee0c2322b8 state: up mac: 48:ee:0c:23:22:b8 Drives: Local Storage: total: 1.14 TiB used: 11.51 GiB (1.0%) ID-1: /dev/sda vendor: Crucial model: CT250MX500SSD1 size: 232.89 GiB ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB Partition: ID-1: / size: 16.21 GiB used: 11.5 GiB (71.0%) fs: ext4 dev: /dev/sda5 ID-2: /boot/efi size: 252 MiB used: 5.2 MiB (2.1%) fs: vfat dev: /dev/sda1 Swap: ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) dev: /dev/sdb2 Sensors: System Temperatures: cpu: 29.8 C mobo: 27.8 C Fan Speeds (RPM): N/A Info: Processes: 246 Uptime: 5h 28m Memory: 7.65 GiB used: 2.08 GiB (27.2%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1869 Shell: Bash v: 5.1.16 inxi: 3.3.13 corrado@corrado-p5-jj-0203:~$ Note: I'm unsure package is gdm3 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 17:18:46 2022 InstallationDate: Installed on 2022-02-08 (39 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session ** Attachment added: "login2.jpg" https://bugs.launchpad.net/bugs/1965627/+attachment/5570780/+files/login2.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965627 Title: Returning from suspend login screen password barely visible Status in gdm3 package in Ubuntu: New Bug description: Returning from suspend login screen password field barely visible. see attachment. corrado@corrado-p5-jj-0203:~$ inxi -Fx System: Host: corrado-p5-jj-0203 Kernel: 5.15.0-23-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 42.beta Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Desktop Mobo: Gigabyte model: H87M-D3H v: x.x serial: UEFI: American Megatrends v: F3 date: 04/24/2013 CPU: Info: dual core model: Intel Core i3-4130 bits: 64 type: MT MCP arch: Haswell rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 2195 high: 2196 min/max: 800/3400 cores: 1: 2195 2: 2195 3: 2195 4: 2196 bogomips: 27136 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel 4th Generation Core Processor Family Integrated Graphics vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0 Display: wayland server: X.Org v: 1.22.1 with: Xwayland v: 22.1.0 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1680x1050~60Hz
[Desktop-packages] [Bug 1962585] Re: tracker-extract-3 crashed with signal 31 in __GI___ioctl()
This bug was fixed in the package tracker-miners - 3.3.0~rc-1 --- tracker-miners (3.3.0~rc-1) experimental; urgency=medium * New upstream release * debian/control.in: Build-Depend on asciidoc-base instead of asciidoc * debian/control.in: Bump minimum gstreamer to 1.20.0 * Cherry-pick patch to fix sandbox crash issue (LP: #1962585) -- Jeremy Bicha Wed, 16 Mar 2022 11:58:22 -0400 ** Changed in: tracker-miners (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1962585 Title: tracker-extract-3 crashed with signal 31 in __GI___ioctl() Status in Tracker: Unknown Status in tracker-miners package in Ubuntu: Fix Released Bug description: Unknown error after first boot Ubuntu Desktop Daily Build 22.04. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: tracker-extract 3.3.0~beta-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 08:24:41 2022 ExecutablePath: /usr/libexec/tracker-extract-3 InstallationDate: Installed on 2022-03-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) ProcCmdline: /usr/libexec/tracker-extract-3 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. Signal: 31 SourcePackage: tracker-miners StacktraceTop: __GI___ioctl (fd=13, request=2148012658) at ../sysdeps/unix/sysv/linux/ioctl.c:36 ?? () from /lib/x86_64-linux-gnu/libblkid.so.1 blkid_probe_set_device () from /lib/x86_64-linux-gnu/libblkid.so.1 blkid_verify () from /lib/x86_64-linux-gnu/libblkid.so.1 blkid_get_dev () from /lib/x86_64-linux-gnu/libblkid.so.1 Title: tracker-extract-3 crashed with signal 31 in __GI___ioctl() 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/tracker/+bug/1962585/+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 1965625] 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/1965625/+attachment/5570759/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1965625/+attachment/5570761/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1965625/+attachment/5570766/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1965625/+attachment/5570767/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1965625/+attachment/5570768/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1965625/+attachment/5570771/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1965625/+attachment/5570772/+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/1965625 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate() Status in gnome-shell package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 15:52:47 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-02-21 (25 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220221) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 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 dialout dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965625/+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 1964923] Re: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964923 Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in update-notifier source package in Jammy: Confirmed Bug description: This bug occurred after install of Ubuntu Mate Jammy daily ISO 15-03-2022 Test machine Dell Optiplex 7060 in UEFI+secure boot mode. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: update-notifier-common 3.192.51 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Mar 15 10:21:14 2022 ExecutablePath: /usr/lib/update-notifier/list-oem-metapackages InstallationDate: Installed on 2022-03-15 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220315) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/lib/update-notifier/list-oem-metapackages Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/lib/update-notifier/list-oem-metapackages'] PythonDetails: N/A SourcePackage: update-notifier Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964923/+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 1964923] Re: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964923 Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in update-notifier source package in Jammy: Confirmed Bug description: This bug occurred after install of Ubuntu Mate Jammy daily ISO 15-03-2022 Test machine Dell Optiplex 7060 in UEFI+secure boot mode. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: update-notifier-common 3.192.51 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Mar 15 10:21:14 2022 ExecutablePath: /usr/lib/update-notifier/list-oem-metapackages InstallationDate: Installed on 2022-03-15 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220315) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/lib/update-notifier/list-oem-metapackages Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/lib/update-notifier/list-oem-metapackages'] PythonDetails: N/A SourcePackage: update-notifier Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964923/+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 1965622] Re: Gnome Shell color sticks to Light mode after selected non-default accent color
Should be fixed by latest: gnome-control-center (1:41.4-1ubuntu8) jammy; urgency=medium * debian/gnome-control-center-data.install, debian/patches/ubuntu/distro-logo.patch, debian/patches/debian/info-overview-Use-the-Vendor-logo-prominently.patch, debian/rules, debian/source/include-binaries, debian/ubuntu-logo-dark.png: - replace the Debian vendor logo patch by the one used in fedora which handle having a dark variant and provides the corresponding image in the package -- Sebastien Bacher Fri, 18 Mar 2022 16:30:25 +0100 gnome-control-center (1:41.4-1ubuntu7) jammy; urgency=medium * debian/ubuntu-logo-icon.png: - use a variant of the logo with the ubuntu label -- Sebastien Bacher Fri, 18 Mar 2022 15:27:28 +0100 ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1965622 Title: Gnome Shell color sticks to Light mode after selected non-default accent color Status in gnome-control-center package in Ubuntu: Incomplete Bug description: 1.) Ubuntu version: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2.) Gnome Control Center version: 1:41.4-1ubuntu6 3.) Expected behavior: Switch Light and Dark in 'Appearance' page change full system colors: app window color and Gnome Shell color (colors of system menu, app icon context menu, etc). 4.) What happened instead: But, after changed accent color from orange to another, system menu, app icon context menu, etc (except desktop & nautilus' context menu) always have Light color. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu6 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 10:20:50 2022 InstallationDate: Installed on 2022-03-06 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1965622/+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 1965624] [NEW] gnome-control-center changes to light theme after selecting options
Public bug reported: After going into Appearance, then selecting Notifications, then Appearance again, the app turns to light theme for some reason. And when you do it again, it goes back to dark. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu8 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 09:13:36 2022 InstallationDate: Installed on 2022-03-09 (10 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-03-17 (2 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/1965624 Title: gnome-control-center changes to light theme after selecting options Status in gnome-control-center package in Ubuntu: New Bug description: After going into Appearance, then selecting Notifications, then Appearance again, the app turns to light theme for some reason. And when you do it again, it goes back to dark. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu8 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 09:13:36 2022 InstallationDate: Installed on 2022-03-09 (10 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-03-17 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965624/+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 Mark York from comment #580) > (In reply to vpi from comment #579) > > (In reply to Mark York from comment #578) > > > (In reply to vpi from comment #577) > > > > (In reply to Darin Miller from comment #563) > > > > > *Ubuntu version: > > > > > > > > > > 1) install kernel build tools: > > > > > (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel): > > > > > > > > > > * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev > > dkms > > > > > libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git > > > > > > > > > > 2) clone the kernel from github and checkout to v5.17 branch (Rather > > > large, > > > > > multiple GB's): > > > > > > > > > > * git clone https://github.com/torvalds/linux.git > > > > > * cd linux > > > > > * git checkout v5.17-rc4 > > > > > > > > > > 3) get the patch and install it: > > > > > > > > > > get the patch form this site and save to "linux" directory: (top > right > > > > > corner "series" button) and use the following "git am ..." line to > > apply > > > > the > > > > > patch: > > > > > > > > > > > > > > > https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4- > > > > > sbind...@opensource.cirrus.com/ > > > > > > > > > > * git am Support-Spi-in-i2c-multi-instantiate-driver.patch > > > > > > > > > > 4) load current kernel config and change configuration then run the > > > > > following scripts/config commands: > > > > > > > > > > * make olddefconfig > > > > > * ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE > > > > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C > > > > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI > > > > > * ./scripts/config --disable CONFIG_DEBUG_INFO > > > > > * ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS "" > > > > > * ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" > > > > > > > > > > 6) build the kernel > > > > > > > > > > * make -j 16 > > > > > > > > > > 7) install the kernel > > > > > > > > > > * sudo make module_install > > > > > * sudo make install > > > > > > > > Hi guys, > > > > > > > > This is my first time compiling a kernel (Legion 7 16ACHg6/Ubuntu > 20.04). > > I > > > > followed these steps (checked out the v5.17-rc8 branch on git) but at > the > > > > end I am getting this error at the last step, just before running sudo > > make > > > > install: > > > > > > > > arch/x86/Makefile:154: CONFIG_X86_X32 enabled but no binutils support > > > > sh ./arch/x86/boot/install.sh 5.17.0-rc8+ \ > > > > arch/x86/boot/bzImage System.map "/boot" > > > > > > > > *** Missing file: arch/x86/boot/bzImage > > > > *** You need to run "make" before "make install". > > > > > > > > make: *** [arch/x86/Makefile:278: install] Error 1 > > > > > > > > Any help would be appreciated > > > > > > > > > Hello @vpi > > > > > > Before running "make install" you need to compile the kernel with "make". > > > "make install" will install the compiled kernel, so you need to compile > it > > > first. > > > > Hi Mark, > > > > I should've been clearer in my last comment. I followed the instructions > > stepwise, which means I ran "make -j 16" before running "make install". And > > yet I was getting this error. > > Hi vpi, > > I would recommend to start fresh. What I would do is: > 1. Get into the kernel config with "make menuconfig", load the .config file > from the "Load" button at the bottom. > 2. Exit the menu, this will save the and accommodate the config. > 3. Compile the kernel with "make" and whatever options you want. > 3. Compile the kernel modules (if you have chosen to build drivers as > modules) with "make modules_install". > 5. Install the kernel image in /boot with "make install". > > Try this and let me know of the results. I'm really interested in fixing > this problem myself as well. I have a Legion 7 16ACHg6 (AMD) and speakers > don't work on Arch Linux. > 4. Since its my first time doing this, I am kinda confused about these steps. When I run "make menuconfig" and try to load the file at path .config in the subsequent screen, it says file does not exist. So where am I supposed to find this? And when you say "Remember to check GRUB's config files to include the new kernel image." what exactly do you mean? Thanks. -- 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
[Desktop-packages] [Bug 1965622] [NEW] Gnome Shell color sticks to Light mode after selected non-default accent color
Public bug reported: 1.) Ubuntu version: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2.) Gnome Control Center version: 1:41.4-1ubuntu6 3.) Expected behavior: Switch Light and Dark in 'Appearance' page change full system colors: app window color and Gnome Shell color (colors of system menu, app icon context menu, etc). 4.) What happened instead: But, after changed accent color from orange to another, system menu, app icon context menu, etc (except desktop & nautilus' context menu) always have Light color. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu6 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 10:20:50 2022 InstallationDate: Installed on 2022-03-06 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1965622 Title: Gnome Shell color sticks to Light mode after selected non-default accent color Status in gnome-control-center package in Ubuntu: New Bug description: 1.) Ubuntu version: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2.) Gnome Control Center version: 1:41.4-1ubuntu6 3.) Expected behavior: Switch Light and Dark in 'Appearance' page change full system colors: app window color and Gnome Shell color (colors of system menu, app icon context menu, etc). 4.) What happened instead: But, after changed accent color from orange to another, system menu, app icon context menu, etc (except desktop & nautilus' context menu) always have Light color. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu6 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 10:20:50 2022 InstallationDate: Installed on 2022-03-06 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1965622/+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 1965535] Re: Stop recommending snap
+1 Agree with the other affected users. The project is not ready to be forced on Ubuntu users - maybe never will. Personally I have two main issues that I can not accept: 1) Forcing automatic software updates without user consent. 2) Putting a hardcoded visible folder into the user home directory without the option to change it. Wish Ubuntu all the best and am very thankful for being my go-to for 17+ years. May those executive decisions make Ubuntu appeal to a broader audience and bring on many new users. Me - personally - I'm expecting to sadly switch distribution with one of the next releases. Once uninstalling snap begins to affect the system in a mayor way. -- 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/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way that decisions are made, are very questionable, and are receiving increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+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 1965610] Re: Extra layouts don't work on Hungarian UI
** Attachment added: "Setting with terminal" https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1965610/+attachment/5570660/+files/extra_layouts.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1965610 Title: Extra layouts don't work on Hungarian UI Status in xkeyboard-config package in Ubuntu: New Bug description: When I set into a terminal the following command: "sudo gsettings set org.gnome.desktop.input-sources show-all-sources true" it fails. We required for "Old Hungarian" layout, short description:"oldhun" -> "Székely-magyar rovásírás" and "Old Hungarian (for ligatures)" layout, short description: "oldhun(lig)" id:"oldhunlig" ->"Székely-magyar rovásírás (ligatúrákhoz)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1965610/+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 1965610] [NEW] Extra layouts don't work on Hungarian UI
Public bug reported: When I set into a terminal the following command: "sudo gsettings set org.gnome.desktop.input-sources show-all-sources true" it fails. We required for "Old Hungarian" layout, short description:"oldhun" -> "Székely-magyar rovásírás" and "Old Hungarian (for ligatures)" layout, short description: "oldhun(lig)" id:"oldhunlig" ->"Székely-magyar rovásírás (ligatúrákhoz)" ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1965610 Title: Extra layouts don't work on Hungarian UI Status in xkeyboard-config package in Ubuntu: New Bug description: When I set into a terminal the following command: "sudo gsettings set org.gnome.desktop.input-sources show-all-sources true" it fails. We required for "Old Hungarian" layout, short description:"oldhun" -> "Székely-magyar rovásírás" and "Old Hungarian (for ligatures)" layout, short description: "oldhun(lig)" id:"oldhunlig" ->"Székely-magyar rovásírás (ligatúrákhoz)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1965610/+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 1798400]
The bug is still there as of LibO 7.3.x. Up in comment 12 (https://bugs.documentfoundation.org/show_bug.cgi?id=120663#c12) there is a nice analysis of the underlying problem why the remote cannot work. Established that, I think that most users go used to the fact that the remote functionality does not work in linux. Personally, I have uninstalled the android app on the phone so I do not have an unfortunate reminder about it. In fact, the real issue is probably the advertisement of a functionality that is not there. For the time being I suggest disabling the remote-via-bluetooth functionality in linux and closing the bug by simply saying that the remote via bluetooth cannot be supported on linux where there are evidently issues that span other software pieces such as the bluetooth stack and pulse audio. To the best of my understanding, these involve the hijacking of the default rfcomm channel by pulse audio before it even needs it and the lack of a standard approach to let other applications find a free channel to use and advertise it to their counterparts. Alternatively (but I would not consider this a good solution), the configuration options could be enhanced to add the possibility to choose a bluetooth channel in libreoffice and in the mobile phone application, so that the user can manually work around the fact that the predefined channel is locked by some other application. As a final point, note that even if the remote-via-wifi may seem a good alternative, in fact in most cases it is practically useless. In most cases, presentations will not be given at a place where you control the network, but at sites with site-provided wifi, such as universities, schools, conference places, business sites, etc. All these locations tend to have wifi deployments that block stuff on the ports used by impress remote. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook
[Desktop-packages] [Bug 1965609] Re: Not all Hunngarian keyboard layouts' name translated to Hungarian layout
** Attachment added: "List of keyboard layout 2nd part" https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1965609/+attachment/5570659/+files/Hungarian_layouts2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1965609 Title: Not all Hunngarian keyboard layouts' name translated to Hungarian layout Status in xkeyboard-config package in Ubuntu: New Bug description: Wen I wanted to choose a Hungarian layout, I saw, that not all Hungarian layouts' name translated into Hungarian language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1965609/+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 1965609] [NEW] Not all Hunngarian keyboard layouts' name translated to Hungarian layout
Public bug reported: Wen I wanted to choose a Hungarian layout, I saw, that not all Hungarian layouts' name translated into Hungarian language. ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Layouts 1st section" https://bugs.launchpad.net/bugs/1965609/+attachment/5570658/+files/Hungarian_layouts1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1965609 Title: Not all Hunngarian keyboard layouts' name translated to Hungarian layout Status in xkeyboard-config package in Ubuntu: New Bug description: Wen I wanted to choose a Hungarian layout, I saw, that not all Hungarian layouts' name translated into Hungarian language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1965609/+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 1965608] [NEW] Crash in gbm_dri_bo_import on ASPEED + AMDGPU system
Public bug reported: I have a server machine with an ASPEED BMC (kernel driver `ast`) and a Radeon Pro WX 4100 (driver `amdgpu`). If I try to log into a KDE Wayland session or a Gnome Wayland session, it crashes back to the login screen, with the same innermost level in the traceback. What I'd like to be able to do: if a monitor is connected to the AMD GPU, then show the login screen on that, and maybe duplicate it on the BMC. If no external monitor is connected, show it only on the BMC. Ideally, it should switch on the fly, but at the very least, it shouldn't crash. Note that in Xorg sessions, it doesn't crash, but xrandr only shows outputs from the AMD GPU. If I do xrandr --listproviders, I see that the `ast` has no capabilities. Provider 0: id: 0x58 cap: 0x9, Source Output, Sink Offload crtcs: 5 outputs: 4 associated providers: 0 name:AMD Radeon (TM) Pro WX 4100 @ pci::0e:00.0 Provider 1: id: 0x99 cap: 0x0 crtcs: 1 outputs: 1 associated providers: 0 name:modesetting It really would be nice to support using it as a dumb output like DisplayLink, even if it has to allow tearing or drop many frames. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libgbm1 21.2.6-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Mar 19 00:09:57 2022 DistUpgraded: 2022-03-15 02:09:53,367 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) (prog-if 00 [VGA controller]) Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:67e3] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:0b0d] InstallationDate: Installed on 2016-10-27 (1969 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=c4c2bc1a-635a-4890-9b75-207bd66db859 ro usbcore.autosuspend=0 earlycon console=ttyS1,115200n8 console=tty0 intel_iommu=on amd_iommu=on plymouth.ignore-serial-consoles pstore.backend=efi drm.debug=0x104 video=efifb:off thunderbolt.dyndbg pcie_ports=native pci=assign-busses,hpbussize=0x33,realloc,hpmmiosize=256M,hpmmioprefsize=1G RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: Upgraded to impish on 2022-03-15 (3 days ago) dmi.bios.date: 08/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: L1.43 dmi.board.name: X570D4U-2L2T dmi.board.vendor: ASRockRack dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrL1.43:bd08/19/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX570D4U-2L2T:rvr:cvnToBeFilledByO.E.M.:ct2:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 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-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu ** Summary changed: - Crash in gbm_dri_bo_import on ASPEED + AMDGPU system (KDE Wayland and Gnome Wayland) + Crash in gbm_dri_bo_import on ASPEED + AMDGPU system -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1965608 Title: Crash in gbm_dri_bo_import on ASPEED + AMDGPU system Status in mesa package in Ubuntu:
