[Desktop-packages] [Bug 1868399] Re: Ghost copies of foreground dialogues when using GNOME Magnifier
It appears this was https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/3305 which was fixed in https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1899 (released in gnome-shell 41.0). ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3305 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3305 ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1868399 Title: Ghost copies of foreground dialogues when using GNOME Magnifier Status in Mutter: New Status in gnome-shell package in Ubuntu: Fix Released Bug description: Affected version Tested with Ubuntu 20.04 current daily build using Xorg. Mutter version 3.36. Bug summary When using the GNOME magnifier feature ghost copies of dialogues such as the Alt+F2 window or the password prompt appear if the magnified view moves away from the dialogue. Steps to reproduce 1. Enable GNOME magnifier by pressing Supper + Alt + 8. 2. Press Alt+F2 to open the command dialogue. 3. Use the mouse to pan around the screen. What happened A slightly fadded copy of the dialogue will move around the screen, keeping its relative position. What did you expect to happen This should not happen. The dialogue should be displayed once and should move appropriately when the magnifier view pans away from it. Upstream Bug: https://gitlab.gnome.org/GNOME/mutter/issues/1100 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.35.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 19:43:49 2020 InstallationDate: Installed on 2020-03-20 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200320) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1868399/+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 1877686] Re: Mouse lags during desktop zoom
I expect this was fixed in GNOME 42, if not earlier. I remember this bug but cannot reproduce it anymore. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- 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/1877686 Title: Mouse lags during desktop zoom Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: After installing ubuntu 20.04, I have an issue with my mouse pointer lagging a lot. It happens on my trackpad, physical mouse, wacom tablet, and trackpoint. It's only a graphical issue (ie: The underlying whatever is actually moving. The visible pointer just isn't). Other mouse moving related actions do not exhibit the same behaviour. Window dragging is smooth. Applications that use custom mouse pointers, such as krita, work smoothly. The issue persists both on nVidia graphics and intel integrated graphics. I am using a lenovo thinkpad p50. The issue persists constantly when I am using the in built laptop screen. However, when I connect a second monitor, it only happens occasionally. I installed ubuntu 20.04 from a usb drive, keeping my home partition from 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 01:28:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:222e] NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e] InstallationDate: Installed on 2020-05-08 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. VFS7500 Touch Fingerprint Sensor Bus 001 Device 002: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 8: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: LENOVO 20EQS2BH00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9eb4b789-a22e-455b-8e8b-19e78e0ef3d6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET86W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EQS2BH00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET86W(1.59):bd08/28/2019:svnLENOVO:pn20EQS2BH00:pvrThinkPadP50:rvnLENOVO:rn20EQS2BH00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EQS2BH00 dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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-xo
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-1982904 stella -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in OEM Priority Project: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+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 1983294] Re: totem is coredumping, ubuntu-bug on the crash file is failing
The most common totem crashes in Ubuntu 22.04 are listed here:
https://errors.ubuntu.com/?release=Ubuntu%2022.04&package=totem&period=week
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1983294
Title:
totem is coredumping, ubuntu-bug on the crash file is failing
Status in totem package in Ubuntu:
Incomplete
Bug description:
Totem is crashing on launch.
I see in /var/crash that the crash was reported, with crash id
affaa5ef-11fd-11ed-a50a-fa163e55efd0, but when I try to run ubuntu-bug
on the crash file it reports this:
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
So that's two different issues -- the crash and the fact that I can't
report it using ubuntu-bug.
I'm hoping you can pull the crash from the ID above and maybe do
something useful with it. :shrug:
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 1 21:12:09 2022
InstallationDate: Installed on 2019-01-02 (1307 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
LogAlsaMixer:
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 15
Mono: Capture 15 [100%] [50.00dB] [on]
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (162 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983294/+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 1983294] Re: totem is coredumping, ubuntu-bug on the crash file is failing
Thanks for the bug report. I am looking at crash ID
affaa5ef-11fd-11ed-a50a-fa163e55efd0 but it doesn't seem to have a stack
trace (yet?). Only that totem crashed with signal 11.
Maybe wait until it happens again and then report a new bug. And if
'ubuntu-bug' fails then 'apport-cli' may work instead.
** Changed in: totem (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1983294
Title:
totem is coredumping, ubuntu-bug on the crash file is failing
Status in totem package in Ubuntu:
Incomplete
Bug description:
Totem is crashing on launch.
I see in /var/crash that the crash was reported, with crash id
affaa5ef-11fd-11ed-a50a-fa163e55efd0, but when I try to run ubuntu-bug
on the crash file it reports this:
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
So that's two different issues -- the crash and the fact that I can't
report it using ubuntu-bug.
I'm hoping you can pull the crash from the ID above and maybe do
something useful with it. :shrug:
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 1 21:12:09 2022
InstallationDate: Installed on 2019-01-02 (1307 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
LogAlsaMixer:
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 15
Mono: Capture 15 [100%] [50.00dB] [on]
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (162 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983294/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-1981676 somerville -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in OEM Priority Project: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+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 1983294] [NEW] totem is coredumping, ubuntu-bug on the crash file is failing
Public bug reported:
Totem is crashing on launch.
I see in /var/crash that the crash was reported, with crash id
affaa5ef-11fd-11ed-a50a-fa163e55efd0, but when I try to run ubuntu-bug
on the crash file it reports this:
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
So that's two different issues -- the crash and the fact that I can't
report it using ubuntu-bug.
I'm hoping you can pull the crash from the ID above and maybe do
something useful with it. :shrug:
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 1 21:12:09 2022
InstallationDate: Installed on 2019-01-02 (1307 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
LogAlsaMixer:
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 15
Mono: Capture 15 [100%] [50.00dB] [on]
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (162 days ago)
** Affects: totem (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1983294
Title:
totem is coredumping, ubuntu-bug on the crash file is failing
Status in totem package in Ubuntu:
New
Bug description:
Totem is crashing on launch.
I see in /var/crash that the crash was reported, with crash id
affaa5ef-11fd-11ed-a50a-fa163e55efd0, but when I try to run ubuntu-bug
on the crash file it reports this:
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
So that's two different issues -- the crash and the fact that I can't
report it using ubuntu-bug.
I'm hoping you can pull the crash from the ID above and maybe do
something useful with it. :shrug:
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 1 21:12:09 2022
InstallationDate: Installed on 2019-01-02 (1307 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
LogAlsaMixer:
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 15
Mono: Capture 15 [100%] [50.00dB] [on]
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (162 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983294/+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 1983292] [NEW] No sound from laptop speakers with Ubuntu 22.04 LTS
Public bug reported: I have sound through bluetooth devices and external headphones but I cannot get sound output from my laptop speakers, at the begining I had "Dummy sound" as the only output device, after some modifications now the default device is HDMI/Display Port but still with no sound , My laptop is a HUAWEI MateBook D15 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: felipe 1485 F pulseaudio /dev/snd/pcmC0D3p: felipe 1485 F...m pulseaudio CasperMD5CheckResult: pass Date: Mon Aug 1 17:30:03 2022 InstallationDate: Installed on 2022-08-01 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=es_CO:es TERM=xterm-256color PATH=(custom, no user) LANG=es_CO.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2021 dmi.bios.release: 1.38 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.38 dmi.board.asset.tag: NULL dmi.board.name: BOHB-WAX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1080 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1080 dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnHUAWEI:bvr1.38:bd11/11/2021:br1.38:efr1.38:svnHUAWEI:pnBOHB-WAX9:pvrM1080:rvnHUAWEI:rnBOHB-WAX9-PCB-B2:rvrM1080:cvnHUAWEI:ct10:cvrM1080:skuC331: dmi.product.family: MateBook D dmi.product.name: BOHB-WAX9 dmi.product.sku: C331 dmi.product.version: M1080 dmi.sys.vendor: HUAWEI ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1983292 Title: No sound from laptop speakers with Ubuntu 22.04 LTS Status in pulseaudio package in Ubuntu: New Bug description: I have sound through bluetooth devices and external headphones but I cannot get sound output from my laptop speakers, at the begining I had "Dummy sound" as the only output device, after some modifications now the default device is HDMI/Display Port but still with no sound , My laptop is a HUAWEI MateBook D15 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: felipe 1485 F pulseaudio /dev/snd/pcmC0D3p: felipe 1485 F...m pulseaudio CasperMD5CheckResult: pass Date: Mon Aug 1 17:30:03 2022 InstallationDate: Installed on 2022-08-01 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=es_CO:es TERM=xterm-256color PATH=(custom, no user) LANG=es_CO.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2021 dmi.bios.release: 1.38 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.38 dmi.board.asset.tag: NULL dmi.board.name: BOHB-WAX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1080 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1080 dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnHUAWEI:bvr1.38:bd11/11/2021:br1.38:efr1.38:svnHUAWEI:pnBOHB-WAX9:pvrM1080:rvnHUAWEI:rnBOHB-WAX9-PCB-B2:rvrM1080:cvnHUAWEI:ct10:cvrM1080:skuC331: dmi.product.family: MateBook D dmi.product.name: BOHB-WAX9 dmi.product.sku: C331 dmi.product.version: M1080 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1983292/+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 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
3v1n0, gtk-module-Handle-display-closing-gracefully.patch introduced regression! Why are you setting d->object to NULL in on_object_disposed? By doing that you are introducing memory leak, no? Creating SoundEventData structure strong reference is added, it must be removed otherwise object will never get finalized!? I am attaching small test app that can be used to reproduce problem - it simply prints warning messages when GObject / GtkWindow is disposed and/or finalized. Basically looks like now canberra-gtk-module adds two extra refs that are not removed. Also with attached test app free_sound_event now is never called with d->object != NULL. ** Attachment added: "Test app" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+attachment/5606320/+files/test-gtk.c -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Won't Fix Status in libcanberra package in Ubuntu: Fix Released Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4 This seems to be a result of Xwayland crashing and gnome-shell then trying to recover (and failing). Although gnome-shell shouldn't be using GTK, and Wayland sessions shouldn't be dependent on having an X11 server (Xwayland) available. Fixing either of those should resolve this. WORKAROUND: sudo apt remove libcanberra-gtk3-module TEST CASE: 1. Log into a Wayland session. 2. Open a Terminal. 3. $ xrandr # Just to ensure Xwayland starts 4. $ killall Xwayland Expected: gnome-shell still responds. Observed: gnome-shell freezes or exits. --- ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 363173] Re: Orca makes cracks, pops, and clicking sound with Festival; eSpeak speaks too fast.
*** This bug is a duplicate of bug 354522 *** https://bugs.launchpad.net/bugs/354522 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: espeak (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to espeak in Ubuntu. https://bugs.launchpad.net/bugs/363173 Title: Orca makes cracks, pops, and clicking sound with Festival; eSpeak speaks too fast. Status in espeak package in Ubuntu: Confirmed Status in gnome-orca package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-orca I've upgraded from 8.10 to 9.04 in my virtual machine and noticed that when using eSpeak synthesizer in Orca, the speech rate seems to be at 100% regardless of what setting I've set to. I'm not sure of the difference in pitch as I've not taken the time to experiment the change of pitch. With Festival, I'm able to control the speech rate just fine, but when I went to speeds over 82, starting 83, it seems to make some weird click and soft-popping sound. What I mean is when I press either the left or right arrow key, it clicks, says a number, and then it makes a low-pitched double pop sound. When I get back to 82, it clicks, says a number, and no double-popping. Even at 82, I Alt+Tab to the Orca main window once and it does not make any popping noise. But when I switch back, it does. Same thing happened with 87, but this does vary depending on which rate I'm in. There are less cracks between 70 to 79. For 69, I heard some 1-millisecond 1-tone beep, but it's probably just a click; however, I'm not sure. I could go on and on, but in general, there are bound to be some cracking noises, regardless of speech rate. This is with RC version of Ubuntu 9.04. Ubuntu 8.10 works just fine with eSpeak and Festival. For previous version of Ubuntu 9.04 (I think it's Alpha 3, but couldn't remember), eSpeak does speak very fast at 100, but most of the time, it goes back to the rate I've set to. For Festival, kal_diphone is the only one selected. For eSpeak, I use the default and also tried English-US, but I don't think it matters anyway. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: gnome-orca 2.26.1-0ubuntu1 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-orca Uname: Linux 2.6.28-11-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/espeak/+bug/363173/+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 1983117] Re: "Focus Follow Mouse" auto-raises windows when it shouldn't
The thread-jack by Bloodyiron on 1969602 #6 is describing the same issue as here, but this is not about Alt-Tab misbehavior, that seems to be something else. None of the other focus issue seem similar. -- 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/1983117 Title: "Focus Follow Mouse" auto-raises windows when it shouldn't Status in mutter package in Ubuntu: New Bug description: Steps to reproduce on Jammy LTS: 1. Create a new empty user and login under Wayland 2. Using gnome-tweaks select "Windows" -> "Window Focus" -> "Focus on Hover" 3. Notice that "Raise Windows When Focused" is disabled Windows auto-raise when changing workspaces: 1. Open two terminal windows and partially overlap them 2. Place the mouse over the lower terminal window so that it remains lowered 3. Do not move the mouse: Press Super-End to change to another workspace, then Super-Begin to go back 4. Observe that the terminal window the mouse is over has been raised The expected behaviour is that windows are not auto-raised when changing workspaces Windows auto-raise when closing windows: 1. Open three terminal windows such that parts of all windows are visible but all windows overlap. 2. Place the mouse inside the topmost terminal so that it is within the visible lowest terminal 3. Without moving the mouse Ctrl-D the terminal to close it 4. Observe that the lowest terminal window the mouse is over has been raised to the top. The expected behaviour is that windows are not auto-raised when closing windows Logout/Login using X and repeat these actions. Notice that window ordering remains fixed in order. This has been the expected behaviour of gnome for the last 10 years or so. This is a behaviour regression for Ubuntu users upgrading from the last LTS (using X). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 12:11:27 2022 InstallationDate: Installed on 2022-06-25 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983117/+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 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
Same... -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+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 1982957] Re: package firefox 102.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Relevant output from DpkgTerminalLog.txt: ==> Installing the firefox snap error: cannot perform the following tasks: - Download snap "firefox" (1589) from channel "stable" (unexpected EOF) This looks like a temporary network failure. Can you run: sudo apt reinstall firefox and let us know how this goes? ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1982957 Title: package firefox 102.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: Incomplete Bug description: It happened while upgrading from 20.4lts to 22.4lts ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 102.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ericmbajerwaka 1727 F pulseaudio /dev/snd/controlC0: ericmbajerwaka 1727 F pulseaudio BuildID: 20220623063721 CasperMD5CheckResult: unknown Channel: Unavailable Date: Wed Jul 27 17:47:54 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2022-07-26 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 10.132.128.1 dev enp0s25 proto dhcp metric 100 10.132.128.0/24 dev enp0s25 proto kernel scope link src 10.132.128.207 metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 102.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-07-27 (0 days ago) dmi.bios.date: 02/24/2020 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.31 dmi.board.name: 2216 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.5B dmi.chassis.asset.tag: 5CG61945TF dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.31:bd02/24/2020:svnHewlett-Packard:pnHPEliteBook840G2:pvrA3009E510303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.5B:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G2 dmi.product.sku: P4C18UC#ABA dmi.product.version: A3009E510303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1982957/+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 1981333] Re: Firefox icon missing from application list
Could it be that you have an old hard copy of /var/lib/snapd/desktop/applications/firefox_firefox.desktop in e.g. ~/.local/share/applications/ ? -- 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/1981333 Title: Firefox icon missing from application list Status in firefox package in Ubuntu: Incomplete Bug description: The icon for Firefox in the applications list on Ubuntu 22.04 has gone missing, as shown in the attached screenshot. The launcher is still there with text only, and clicking on it opens Firefox with no issue. This is the default installation of Firefox, not modified or replaced by me. To be specific, snap lists Firefox as version 102.0.1-1 and revision 1551. I have the Steam and Chrome apt repositories, but my list of apt packages has nothing mentioning Firefox. Because I use Chrome instead, I'm mostly reporting this because it should be fixed for everyone else who may run into this problem, I don't need instructions on how to fix it myself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981333/+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 1981872] Re: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 10
Relevant output from DpkgTerminalLog.txt: error: snap "firefox" has "install-snap" change in progress This looks like a transient problem, where the firefox snap was already being installed. Can you run: sudo apt reinstall firefox And let us know whether it succeeds? ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1981872 Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 10 Status in firefox package in Ubuntu: Incomplete Bug description: I find this bug when i install firefox ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jul 16 13:05:30 2022 Dependencies: ErrorMessage: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 10 InstallationDate: Installed on 2022-07-16 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: firefox Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981872/+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 1981286] Re: Firefox will not start if home folder not in /home
There is currently no plan to revert to shipping firefox as a deb (although nothing is ever written in stone). As such, I'm setting the status of the bug to "Won't Fix", and I suggest you watch bug #1620771 for progress on the issue that affects all snap applications. ** Changed in: firefox (Ubuntu) Status: Incomplete => Won't Fix -- 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/1981286 Title: Firefox will not start if home folder not in /home Status in firefox package in Ubuntu: Won't Fix Bug description: When a user's home directory is not in /home Firefox will not start. If I try to start Firefox from the command line the following message is output. Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. It appears this is a result of the decision to use Snap to install Firefox. If so then this shouldn't have happened until the limitation on Snap had been removed. Kubuntu 22.04 Firefox 102.0.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981286/+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 1981881] Re: Firefox snap broken in Guest Account
*** This bug is a duplicate of bug 1593407 *** https://bugs.launchpad.net/bugs/1593407 Firefox in 16.04 wasn't installed as a snap, whereas in 22.04 it is a snap by default. So it is indeed a duplicate of bug #1593407. -- 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/1981881 Title: Firefox snap broken in Guest Account Status in firefox package in Ubuntu: New Bug description: My laptop is sometimes used by visitors. They want to browse the internet. So I setup the guest-account. I found out that the Firefox snap is broken on guest-accounts. When opening Firefox nothing happens. When starting FF from the command line of the guest-account I found out the following: $ firefox 2022/07/12 00:46:01.906615 tool_linux.go:82: cannot open snapd info file “/snap/snapd/current/usr/lib/snapd/info”: open /snap/snapd/current/usr/lib/snapd/info: permission denied Version information: Guest Account on Xubuntu 22.04 (Jammy) FF version: 102.0.1 (64-bit) Mozilla Firefox Snap for Ubuntu canonical-002-1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981881/+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 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
Yes, I have updated the patch in kinetic, and I will SRU it in jammy.
This will require using a new bug report though, maybe bug #1967963 ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in Xdg-utils:
New
Status in xdg-utils package in Ubuntu:
Fix Released
Status in xdg-utils source package in Jammy:
Fix Released
Bug description:
[Impact]
The firefox snap (default in 22.04) will always report that it thinks
it's not the default browser (even when it actually is) for KDE users
(this can be seen when browsing to about:preferences).
This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
specific functions whereas the default interpreter is dash).
The fix is rather trivial and will visibly improve the UX for those
users.
[Test Plan]
In Kubuntu 22.04:
- make sure firefox isn't your default browser (by changing the setting to a
different browser)
- run the firefox snap, browse to "about:preferences", and observe that
firefox claims NOT to be the default browser
- click the "Set default" button
- refresh the page (F5)
- observe that now firefox claims to be the default browser
- in a terminal, execute `xdg-open https://example.org`, and verify that the
page is open in the firefox snap
[Where problems could occur]
The patch is changing KDE-specific functions (check_browser_kde and
check_url_scheme_handler_kde), so in theory it shouldn't affect
running xdg-utils in any other desktop environment.
If the proposed patch is incorrect, it would affect the functionality
of `xdg-settings check default-web-browser` and `xdg-settings check
default-url-scheme-handler`, so this is what needs to be thoroughly
tested in KDE.
In the event of a regression, these functions wouldn't work as
expected (they already don't, so the user wouldn't observe a
functional regression, merely the absence of a fix).
[Original description]
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+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 1980804] Re: New bugfix release 22.0.5
This bug was fixed in the package mesa - 22.0.5-0ubuntu0.1 --- mesa (22.0.5-0ubuntu0.1) jammy; urgency=medium * New upstream release. (LP: #1980804) - add 00-radv-defaults.conf to mesa-vulkan-drivers -- Timo Aaltonen Wed, 06 Jul 2022 09:37:40 +0300 ** Changed in: mesa (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1980804 Title: New bugfix release 22.0.5 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Released Bug description: [Impact] This is the last point-release of the 22.0.x-series, we should put it in jammy so latest bugfixes would get there, and in focal for 20.04.5 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1980804/+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 1981966] Re: [SRU] libreoffice 7.3.5 for jammy
This bug was fixed in the package libreoffice - 1:7.3.5-0ubuntu0.22.04.1 --- libreoffice (1:7.3.5-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #1981966) -- Rico Tzschichholz Sat, 16 Jul 2022 12:39:11 +0200 ** Changed in: libreoffice (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1981966 Title: [SRU] libreoffice 7.3.5 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Released Bug description: [Impact] * LibreOffice 7.3.5 is in its fifth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.5_release * Version 7.3.4 is currently released in jammy. For a list of fixed bugs compared to 7.3.4 see the list of bugs fixed in the release candidates of 7.3.5 (that's a total of 83 bugs): https://wiki.documentfoundation.org/Releases/7.3.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.5/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1797/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220719_091411_74233@/log.gz * [arm64] ... * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220719_110142_388ca@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220719_082728_0b9aa@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220719_080609_7c067@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 83 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1981966/+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 1980804] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1980804 Title: New bugfix release 22.0.5 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Released Bug description: [Impact] This is the last point-release of the 22.0.x-series, we should put it in jammy so latest bugfixes would get there, and in focal for 20.04.5 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1980804/+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 1981966] Update Released
The verification of the Stable Release Update for libreoffice has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1981966 Title: [SRU] libreoffice 7.3.5 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Released Bug description: [Impact] * LibreOffice 7.3.5 is in its fifth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.5_release * Version 7.3.4 is currently released in jammy. For a list of fixed bugs compared to 7.3.4 see the list of bugs fixed in the release candidates of 7.3.5 (that's a total of 83 bugs): https://wiki.documentfoundation.org/Releases/7.3.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.5/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1797/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220719_091411_74233@/log.gz * [arm64] ... * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220719_110142_388ca@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220719_082728_0b9aa@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220719_080609_7c067@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 83 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1981966/+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 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
Encountered same issue today, its super annoying as none of the workarounds work, looking for a fix asap. -- 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/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+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
Re: [Desktop-packages] [Bug 1983112] Re: Appstream does not install config file
As far as I can tell, this only happens during deployment when installing the ubuntu-desktop-minimal (haven't tried with the full-fat ubuntu-desktop package) via the new Ubuntu automated server install method. So probably is an Ubuntu-specific issue. I will try to do more testing and narrow down the exact combination of events causing this. On 01/08/2022 10:23, Matthias Klumpp wrote: > Very odd... There is nothing special about this config file (it's installed > like every other) and this works absolutely fine on Debian and even my Ubuntu > VM. > So, something very odd and possibly uBUNTU-SPECIFIC is going on here... > -- James Paton-Smith Linux Support Officer EBI Systems Application Group, South Building, Studio 12 European Bioinformatics Institute (EMBL-EBI) Wellcome Trust Genome Campus Hinxton Cambridge CB10 1SD +44 (0)1223 494308 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983144] Re: Make thunderbird recognize irc: system-handler
Please also check the upstream bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=953953 https://bugzilla.mozilla.org/show_bug.cgi?id=1782485 ** Bug watch added: Mozilla Bugzilla #953953 https://bugzilla.mozilla.org/show_bug.cgi?id=953953 ** Bug watch added: Mozilla Bugzilla #1782485 https://bugzilla.mozilla.org/show_bug.cgi?id=1782485 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1983144 Title: Make thunderbird recognize irc: system-handler Status in thunderbird package in Ubuntu: New Bug description: Ubuntu 22.04 @ 29/07/2022 Current case: Thunderbird is installed by default on ubuntu and has a built-in chat/irc client but when clicking irc/ircs links on a browser system-handler does not recognize thunderbird as default irc client Wishlist: Please make Thunderbird open irc links to open with its built-in chat client so users can find their favorite irc (support) channels easy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1 Uname: Linux 5.17.7-051707-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1007 F pulseaudio BuildID: 20220628000715 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 20:25:54 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IpRoute: default via 192.168.1.1 dev enp1s0f1 proto dhcp metric 100 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev enp1s0f1 scope link metric 1000 192.168.1.0/24 dev enp1s0f1 proto kernel scope link src 192.168.1.34 metric 100 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.63 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile0PrefSources: prefs.js Profile0Prefs: extensions.lastAppVersion: "91.11.0" (prefs.js) network.trr.blocklist_cleanup_done: true (prefs.js) Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.11.0/20220628000715 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983144/+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 1983112] Re: Appstream does not install config file
Very odd... There is nothing special about this config file (it's installed like every other) and this works absolutely fine on Debian and even my Ubuntu VM. So, something very odd and possibly uBUNTU-SPECIFIC is going on here... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1980873] Re: New release 103.0.5060.53 for Bionic
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/1980873 Title: New release 103.0.5060.53 for Bionic Status in chromium-browser package in Ubuntu: Fix Released Bug description: A new upstream release 103.0.5060.53 is available. Debian released a security advisory on June 22. Please package it for Bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1980873/+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 1972977] Re: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query()
I misinterpreted mesa's branching structure. The commit is indeed in 22.2 (not tagged yet). ** Tags removed: fixed-in-23 ** Tags added: fixed-in-22.2 -- 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/1972977 Title: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: New Status in mesa package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1972977/+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 1002958] Re: Moving external monitor around hard-locks x
Maybe open a new bug from an affected system if you find any similar bugs in more recent releases. ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1002958 Title: Moving external monitor around hard-locks x Status in xorg-server package in Ubuntu: Won't Fix Status in xorg-server source package in Precise: Won't Fix Bug description: On a Lenovo Thinkpad X220:- 1. Attach external screen to the displayport connector via HDMI adapter 2. Boot the computer 3. Login 4. Observe all okay until running the display system settings applet and move the external display above (behind) the laptop display. X crashes to the point I have to use Alt+SysRq to reboot. I can run with the displays side-by-side but not one above the other. (my desk arrangement has the external display behind my laptop not side-by-side). I can recover the situation by moving ~/.config/monitors.xml out the way. I have attached my monitors.xml which may have some configuration issue causing the crash in X. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Tue May 22 16:09:28 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120203) MachineType: LENOVO 4287CTO ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=86ea7114-6b69-4161-b91c-44ccb7fcfd67 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET52WW (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET52WW(1.22):bd09/15/2011:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1002958/+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 1983185] Re: Recent commit breaks /etc/X11/Xsession
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1983185 Title: Recent commit breaks /etc/X11/Xsession Status in xorg package in Ubuntu: Confirmed Status in xorg package in Debian: Unknown Bug description: The following command: $/etc/X11/Xsession true opens a dialog with the following error message: "Xsession: unable to launch "true" X session --- "true" not found; falling back to default session." There is a "Okay" button on this message, and clicking it does bad things if one happens to be running Ubuntu 22.04 on Xorg (or running Gnome on Xorg, which is seemingly a different option for the the low latency installation I am running: 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux). See Brendan O'Dea's related comment about this behavior on debian- bugs-dist: https://www.mail-archive.com/debian-bugs- d...@lists.debian.org/msg1857023.html This has consequences in my use of xpra. For example, if I use xpra via the run_scaled-master script to magnify a single application's interface for a 4K display I get the error dialog mentioned above, often with resulting system instability. This behavior cropped up last month. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sat Jul 30 10:14:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.34, 5.15.0-41-lowlatency, x86_64: installed virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2269] NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269] InstallationDate: Installed on 2022-07-13 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20MBCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_aze0rg@/vmlinuz-5.15.0-43-generic root=ZFS=rpool/ROOT/ubuntu_aze0rg ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: N2CET64W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN2CET64W(1.47):bd06/10/2022:br1.47:efr1.16:svnLENOVO:pn20MBCTO1WW:pvrThinkPadP72:rvnLENOVO:rn20MBCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20MB_BU_Think_FM_ThinkPadP72: dmi.product.family: ThinkPad P72 dmi.product.name: 20MBCTO1WW dmi.product.sku: LENOVO_MT_20MB_BU_Think_FM_ThinkPad P72 dmi.product.version: ThinkPad P72 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubun
[Desktop-packages] [Bug 1983112] Re: Appstream does not install config file
No, I did not remove the config file manually. We're actually using the attached bash script as a late-command in the autoinstall as a workaround to fix the issue. Without this script, the snap-store simply refuses to show .deb packages from the repos. ** Attachment added: "appstream_config_reinstall" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5606252/+files/appstream_fix.sh -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983185] Re: Recent commit breaks /etc/X11/Xsession
** Bug watch added: Debian Bug tracker #1012474 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012474 ** Also affects: xorg (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012474 Importance: Unknown Status: Unknown -- 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/1983185 Title: Recent commit breaks /etc/X11/Xsession Status in xorg package in Ubuntu: Confirmed Status in xorg package in Debian: Unknown Bug description: The following command: $/etc/X11/Xsession true opens a dialog with the following error message: "Xsession: unable to launch "true" X session --- "true" not found; falling back to default session." There is a "Okay" button on this message, and clicking it does bad things if one happens to be running Ubuntu 22.04 on Xorg (or running Gnome on Xorg, which is seemingly a different option for the the low latency installation I am running: 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux). See Brendan O'Dea's related comment about this behavior on debian- bugs-dist: https://www.mail-archive.com/debian-bugs- d...@lists.debian.org/msg1857023.html This has consequences in my use of xpra. For example, if I use xpra via the run_scaled-master script to magnify a single application's interface for a 4K display I get the error dialog mentioned above, often with resulting system instability. This behavior cropped up last month. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sat Jul 30 10:14:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.34, 5.15.0-41-lowlatency, x86_64: installed virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2269] NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269] InstallationDate: Installed on 2022-07-13 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20MBCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_aze0rg@/vmlinuz-5.15.0-43-generic root=ZFS=rpool/ROOT/ubuntu_aze0rg ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: N2CET64W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN2CET64W(1.47):bd06/10/2022:br1.47:efr1.16:svnLENOVO:pn20MBCTO1WW:pvrThinkPadP72:rvnLENOVO:rn20MBCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20MB_BU_Think_FM_ThinkPadP72: dmi.product.family: ThinkPad P72 dmi.product.name: 20MBCTO1WW dmi.product.sku: LENOVO_MT_20MB_BU_Think_FM_ThinkPad P72 dmi.product.version: ThinkPad P72 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xse
[Desktop-packages] [Bug 1983183] Re: miss button on pop up window due to notification server limiation
This is certainly not a xorg bug. My first guess would be libnotify.
** Package changed: xorg (Ubuntu) => libnotify (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/1983183
Title:
miss button on pop up window due to notification server limiation
Status in libnotify package in Ubuntu:
New
Bug description:
Hi,
This issue is related with emacs and ubuntu gnome. In emacs if we eval
below code:
(progn (require 'notifications)
(notifications-notify
:title "only show aa bb cc"
:body "d e are missing"
:timeout 10
:urgency :normal
:actions '("a" "aa" "b" "bb" "c" "cc" "d" "dd" "e" "ee")
:on-action (lambda (id key) (message "id: %s key: %s" id key
There should be 5 buttons shown on pop up window, "aa", "bb", "cc", "dd",
"ee". But it only shows three button "aa", "bb" and "cc", the other two button
"dd" and "ee" are missing.
I have issue this bug to emacs
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56834, but they conclude this is
notification server limitation, so I suppose I should issue the bug here, hope
issue can be solved here.
related information:
lsb_release -rd
1 ↵
Description: Ubuntu 20.04.4 LTS
Release: 20.04
emacs version:
GNU Emacs 28.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.20, cairo
version 1.16.0) of 2022-06-24
notification server information:
(notifications-get-server-information);; this code is run from emacs which
shows the notification server information.
outout is: ("gnome-shell" "GNOME" "3.36.9" "1.2")
neofetch output:
neofetch
130 ↵
.-/+oooo+/-. wangzongtao@X570
`:+ss+:`
-+ssyy+- OS: Ubuntu 20.04.4 LTS x86_64
.ossdMMMNyo. Kernel: 5.15.0-41-generic
/ssshdmmNNmmyNhss/ Uptime: 5 days, 5 hours, 40 mins
+shmydMMMNy+ Packages: 3077 (dpkg), 18 (snap)
/hNMMMyhhhmNMMMNh/Shell: zsh 5.8
.dMMMNhsshNMMMd. Resolution: 3840x2160
+hhhyNMMNyyNMMMysss+ DE: GNOME 3.36.9
ossyNMMMNyMMhsshmmmhssso WM: Mutter
ossyNMMMNyMMhsshmmmhssso WM Theme: Adwaita
+hhhyNMMNyyNMMMysss+ Theme: Yaru [GTK2/3]
.dMMMNhsshNMMMd. Icons: breeze [GTK2/3]
/hNMMMyhhhdNMMMNh/Terminal: gnome-terminal
+sdmydy+ CPU: AMD Ryzen 9 3900X (24) @
3.800GHz
/ssshdmmyNhss/ GPU: NVIDIA 09:00.0 NVIDIA
Corporation Device 2204
.ossdMMMNyo. Memory: 10957MiB / 128728MiB
-+syyy+-
`:+ss+:`
.-/+oooo+/-.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..09.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 495.29.05 Thu Sep 30
16:00:29 UTC 2021
GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 30 23:21:46 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
nvidia, 495.29.05, 5.13.0-52-generic, x86_64: installed
nvidia, 495.29.05, 5.15.0-41-generic, x86_64: installed
virtualbox, 6.1.34, 5.13.0-52-generic, x86_64: installed
virtualbox, 6.1.34, 5.15.0-41-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
NVIDIA Corporation Device [10de:2204] (rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device [10de:1454]
InstallationDate: Installed on 2021-09-10 (323 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOO
