[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Problem has NOT been fixed for my setup: - Kernel: 5.4.0-58.64-generic - OS: Ubuntu 20.04.1 LTS - Machine: Dell Inspiron 7559 (0706) - Headset: Anker Soundcore Liberty Air 2 -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Problem has NOT been fixed for my setup: - Kernel: 5.4.0-58.64-generic - OS: Ubuntu 20.04.1 LTS - Machine: Dell Inspiron 7559 (0706) - Headset: Anker Soundcore Liberty Air 2 -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1893792] Re: very tiny fonts on top bar. I downgraded libmutter package temporarily as a workaround
*** This bug is a duplicate of bug 1892440 *** https://bugs.launchpad.net/bugs/1892440 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1893792 Title: very tiny fonts on top bar. I downgraded libmutter package temporarily as a workaround Status in mutter package in Ubuntu: Confirmed Bug description: The temporary solution is: sudo apt install libmutter-6-0=3.36.1-3ubuntu3 gir1.2-mutter-6=3.36.1-3ubuntu3 sudo apt-mark hold libmutter-6-0 This bug seems to be realated to nvdia graphic cards drivers as there is no bug when using the open source nvidia driver. Waiting for you to find a solution guys. I'm not the only one with this bug. I've found the temporary solution on the net. Thank-you ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.4-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 10:12:44 2020 InstallationDate: Installed on 2020-08-24 (8 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash 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/1893792/+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 1909857] [NEW] NUC7i5 - No HBR, unstable EAC3 audio passthrough on Ubuntu 20.10
Public bug reported:
Software is X11-based stable/up-to-date Kodi v18 on up-to-date Ubuntu 20.10.
Hardware is an Intel NUC7i5BNH (Kaby Lake), latest available BIOS and latest
available HDMI/LS-PCON firmware. The AVR is a Denon AVR-2310. The TV is an old
Toshiba 1080p LCD. I make sure that the TV and AVR are turned on first so that
EDID is available.
When playing a file with HBR audio bitstreams (DTS-HD, Dolby TrueHD) I get no
audio.
When playing a file with EAC3/DD+ audio bitstreams, I get very regular dropouts.
When I play a file with stereo/DTS/DD bitstreams, all is fine.
When I play an audio file with 6 channels of LPCM, all is fine.
I can play the same files with HBR or EAC3 audio on the same machine from a
Windows install without any issue, right out of the box using the built-in
software, using the default configs, which rules out hardware incompatibilities.
I've spent some time with the Kodi guys who have come to the conclusion that
the issue was not with them but higher in the software stack. So here I am!
History here: https://forum.kodi.tv/showthread.php?tid=359371
I've also filed a bug with Intel, but I'm not getting any traction there. Must
be the holydays!
https://gitlab.freedesktop.org/drm/intel/-/issues/2861
Any help is welcomed.
I'm no dev, but I know my way around Linux and systems, and I am not
afraid of testing things and reporting data. Compiling code is usually
something I can do, with instructions if it's less run-of-the-mill.
Thanks in advance!
More specific/detailed background data:
BIOS: BNKBL357.86A.0083.2020.0714.1344 07/14/2020 (latest available from Intel)
HDMI Firmware: 1.77.93 (the latest available from Intel, updated from a Windows
install)
System architecture: ("uname -m"): x86_64
Kernel version: ("uname -r"): 5.8.0-33-generic
Linux distribution: Ubuntu 20.10 kept up-to-date
Machine or motherboard model (use dmidecode if needed): NUC7i5BNH -
https://paste.ubuntu.com/p/J2V4mKFWSg/
Display connector: physically HDMI, but I understand that it is internally a DP
with a protocol converter leading to HDMI
Full dmesg with debug information: From boot
https://paste.ubuntu.com/p/53qVzpDJ76/
I've played a file with DTS-HD HBR audio bitstream (no audio) towards the end,
if it can help - https://paste.ubuntu.com/p/5pRRpmfT3P/
I've played a file with EAC3 audio bitstream with dropouts towards the end of
that one, if it can help - https://paste.ubuntu.com/p/xFPQY5Zzcb/
xrandr --verbose: https://paste.ubuntu.com/p/V95ZWx9MNy/
intel_reg_dumper output: https://paste.ubuntu.com/p/bWnjsvQ9t4/
VBIOS dump: File available there https://youplala.net/~nico/intel/
lsmod | grep snd: https://paste.ubuntu.com/p/hq9Bf87GbY/
/proc/asound/card0/codec#2: https://paste.ubuntu.com/p/8JDwbj5pYs/
/proc/asound/card0/eld#2.0: https://paste.ubuntu.com/p/KdZzHZxTsm/
cat /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid |
edid-decode: https://paste.ubuntu.com/p/vVjdSWh9Dz/
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base (not installed)
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jan 2 12:59:50 2021
InstallationDate: Installed on 2018-02-01 (1066 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64
(20180108.1)
ProcEnviron:
LANGUAGE=en_GB:en
TERM=screen-256color
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to groovy on 2020-12-26 (7 days ago)
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug groovy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1909857
Title:
NUC7i5 - No HBR, unstable EAC3 audio passthrough on Ubuntu 20.10
Status in alsa-driver package in Ubuntu:
New
Bug description:
Software is X11-based stable/up-to-date Kodi v18 on up-to-date Ubuntu 20.10.
Hardware is an Intel NUC7i5BNH (Kaby Lake), latest available BIOS and latest
available HDMI/LS-PCON firmware. The AVR is a Denon AVR-2310. The TV is an old
Toshiba 1080p LCD. I make sure that the TV and AVR are turned on first so that
EDID is available.
When playing a file with HBR audio bitstreams (DTS-HD, Dolby TrueHD) I get no
audio.
When playing a file with EAC3/DD+ audio bitstreams, I get very regular
dropouts.
When I play a file with stereo/DTS/DD bitstreams, all is fine.
When I play an audio file with 6 channels of LPCM, all is fine.
I can play the same files with HBR or EAC3 audio on the same machine from a
Windows install without any issue, right out of the box using the built-in
software, using the default configs, which rules out hardware incompatibilities.
I've spent some time with the Kodi guys who have come to the conclusion that
the is
[Desktop-packages] [Bug 1909857] Re: NUC7i5 - No HBR, unstable EAC3 audio passthrough on Ubuntu 20.10
Also, alsa-info.sh: https://paste.ubuntu.com/p/sspkGCwkVj/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1909857
Title:
NUC7i5 - No HBR, unstable EAC3 audio passthrough on Ubuntu 20.10
Status in alsa-driver package in Ubuntu:
New
Bug description:
Software is X11-based stable/up-to-date Kodi v18 on up-to-date Ubuntu 20.10.
Hardware is an Intel NUC7i5BNH (Kaby Lake), latest available BIOS and latest
available HDMI/LS-PCON firmware. The AVR is a Denon AVR-2310. The TV is an old
Toshiba 1080p LCD. I make sure that the TV and AVR are turned on first so that
EDID is available.
When playing a file with HBR audio bitstreams (DTS-HD, Dolby TrueHD) I get no
audio.
When playing a file with EAC3/DD+ audio bitstreams, I get very regular
dropouts.
When I play a file with stereo/DTS/DD bitstreams, all is fine.
When I play an audio file with 6 channels of LPCM, all is fine.
I can play the same files with HBR or EAC3 audio on the same machine from a
Windows install without any issue, right out of the box using the built-in
software, using the default configs, which rules out hardware incompatibilities.
I've spent some time with the Kodi guys who have come to the conclusion that
the issue was not with them but higher in the software stack. So here I am!
History here: https://forum.kodi.tv/showthread.php?tid=359371
I've also filed a bug with Intel, but I'm not getting any traction there.
Must be the holydays!
https://gitlab.freedesktop.org/drm/intel/-/issues/2861
Any help is welcomed.
I'm no dev, but I know my way around Linux and systems, and I am not
afraid of testing things and reporting data. Compiling code is usually
something I can do, with instructions if it's less run-of-the-mill.
Thanks in advance!
More specific/detailed background data:
BIOS: BNKBL357.86A.0083.2020.0714.1344 07/14/2020 (latest available from
Intel)
HDMI Firmware: 1.77.93 (the latest available from Intel, updated from a
Windows install)
System architecture: ("uname -m"): x86_64
Kernel version: ("uname -r"): 5.8.0-33-generic
Linux distribution: Ubuntu 20.10 kept up-to-date
Machine or motherboard model (use dmidecode if needed): NUC7i5BNH -
https://paste.ubuntu.com/p/J2V4mKFWSg/
Display connector: physically HDMI, but I understand that it is internally a
DP with a protocol converter leading to HDMI
Full dmesg with debug information: From boot
https://paste.ubuntu.com/p/53qVzpDJ76/
I've played a file with DTS-HD HBR audio bitstream (no audio) towards the
end, if it can help - https://paste.ubuntu.com/p/5pRRpmfT3P/
I've played a file with EAC3 audio bitstream with dropouts towards the end of
that one, if it can help - https://paste.ubuntu.com/p/xFPQY5Zzcb/
xrandr --verbose: https://paste.ubuntu.com/p/V95ZWx9MNy/
intel_reg_dumper output: https://paste.ubuntu.com/p/bWnjsvQ9t4/
VBIOS dump: File available there https://youplala.net/~nico/intel/
lsmod | grep snd: https://paste.ubuntu.com/p/hq9Bf87GbY/
/proc/asound/card0/codec#2: https://paste.ubuntu.com/p/8JDwbj5pYs/
/proc/asound/card0/eld#2.0: https://paste.ubuntu.com/p/KdZzHZxTsm/
cat /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid |
edid-decode: https://paste.ubuntu.com/p/vVjdSWh9Dz/
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base (not installed)
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jan 2 12:59:50 2021
InstallationDate: Installed on 2018-02-01 (1066 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64
(20180108.1)
ProcEnviron:
LANGUAGE=en_GB:en
TERM=screen-256color
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to groovy on 2020-12-26 (7 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1909857/+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 1909862] [NEW] System setting is not working
Public bug reported: System setting is not working with my hp lap top. There is no icon available in the menu and settings like display and background are not active ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1909862 Title: System setting is not working Status in alsa-driver package in Ubuntu: New Bug description: System setting is not working with my hp lap top. There is no icon available in the menu and settings like display and background are not active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1909862/+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 364091] Re: xrandr error with delmode
I'm still experiencing this problem with 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/364091 Title: xrandr error with delmode Status in x11-xserver-utils package in Ubuntu: Confirmed Bug description: Binary package hint: x11-xserver-utils Ubuntu 9.04 Realase Candidate, i386 My setup: Sapphire 2600 XT AGP + Compaq P1100 monitor (maximux resolution supported 1920x1440) connected via DVI port Output of xrandr Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 2048 x 1600 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 380mm x 290mm 2048x1536 60.0 1920x1440 75.0 60.0 1856x1392 75.0 60.0 1792x1344 75.0 60.0 1600x1200 85.0*75.0 70.0 65.0 60.0 1680x1050 84.9 74.9 69.9 60.0 1600x1024 60.2 1400x1050 85.0 74.8 70.0 60.0 1280x1024 85.0 75.0 60.0 1440x900 59.9 1280x960 85.0 60.0 1360x768 59.8 1152x864 100.0 85.1 85.0 75.0 75.0 70.0 60.0 1024x768 85.0 75.0 70.1 60.0 43.5 832x62474.6 800x60085.1 85.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 75.0 66.7 59.9 720x40087.8 85.0 70.1 640x40085.1 640x35085.1 VGA-0 disconnected (normal left inverted right x axis y axis) Maximum default resolution "2048 x 1600" reported, is wrong for Compaq P1100 monitor and i tried to delete with the command: $ xrandr --delmode DVI-0 2048x1536 X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 150 (RANDR) Minor opcode of failed request: 19 () Serial number of failed request: 23 Current serial number in output stream: 24 Note: GDM (Login Screen) Bad Screen Refresh Rate [lspci] 00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface [8086:2570] (rev 02) Subsystem: ASRock Incorporation Device [1849:2570] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV 630 XT AGP [Radeon HD 2600 XT AGP] [1002:9586] Subsystem: PC Partner Limited Device [174b:0028] --- Architecture: i386 CurrentDmesg: [ 24.596026] eth0: no IPv6 routers present [ 26.752026] end_request: I/O error, dev fd0, sector 0 [ 26.784033] end_request: I/O error, dev fd0, sector 0 DistroRelease: Ubuntu 10.04 DkmsStatus: Error: [Errno 2] No such file or directory InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) Package: x11-xserver-utils 7.5+1ubuntu2 PackageArchitecture: i386 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=11fd8e9e-15b4-4eba-bb1d-434d4d5282b3 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Tags: lucid lucid Uname: Linux 2.6.32-21-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.72 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.72:bd11/07/2008:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/364091/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%
kms doesn't work for me, it scales the entire resolution to 125% so much of the screen just falls off of my display to the right and bottom. My setup is an asus rog g14 hooked up (via hdmi) to a 4k monitor. With the intel hardware fractional scaling works perfectly, so for most things I can simply run using the nvidia hybrid mode and launch applications using dedicated graphics card when I need to. However, blender specifically can still be quite slow in this mode and much faster in nvidia performance mode, but hardly usable since the text in the app is so small. Really hoping for a solution here! I'm almost always plugged into a desktop setup with this laptop so I'd much rather just run performance mode when working on anything serious. More info - Ubuntu 20.10, RTX 2060, I've tried nvidia drivers 450 and 455. -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1909877] [NEW] Clock in top bar doesn't update
Public bug reported: When exiting fullscreen from chromium (YouTube), the clock widget in the top bar seems stuck and only updates after being updated from the mouse hovering over it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 2 21:56:27 2021 DistUpgraded: 2020-12-27 18:29:34,023 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-58-generic, x86_64: installed nvidia, 455.45.01, 5.8.0-33-generic, x86_64: installed virtualbox, 6.1.14, 5.4.0-58-generic, x86_64: installed virtualbox, 6.1.14, 5.8.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1265] InstallationDate: Installed on 2020-12-11 (22 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic root=UUID=8753fbc2-cbcd-41b4-ad44-9e1a6f940ddf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-12-27 (6 days ago) dmi.bios.date: 08/05/2019 dmi.bios.release: 1.28 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:br1.28:efr1.26:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.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-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy 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/1909877 Title: Clock in top bar doesn't update Status in xorg package in Ubuntu: New Bug description: When exiting fullscreen from chromium (YouTube), the clock widget in the top bar seems stuck and only updates after being updated from the mouse hovering over it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.r
[Desktop-packages] [Bug 1209095] Re: Thunderbird hogs CPU while waiting for master password
Launchpad has imported 31 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=791535. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-09-16T09:13:30+00:00 toralf wrote: User Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20100101 Firefox/15.0.1 Build ID: 20120907154448 Steps to reproduce: started Thunderbird and forgot to type in the password Actual results: 4-core CPU is up to 100%, fan is very noisy Expected results: a (milli)sleep in that source code loop to keep my ThinkPad quiet and cool Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1209095/comments/0 On 2012-10-09T15:48:32+00:00 toralf wrote: maybe a blinking task bar window should be enough for forgetful people like me. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1209095/comments/1 On 2012-12-04T18:18:00+00:00 Vseerror wrote: I see this with imap account Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1209095/comments/2 On 2012-12-04T19:09:45+00:00 Vseerror wrote: steps 1. start thunderbird 2. click on imap account folder where it is set to check for new messages at X interval and does NOT have account password saved. results: password prompt comes up progress meter spins not 100% reproducible after first occurrence, unless you restart thunderbird Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1209095/comments/3 On 2012-12-04T20:12:54+00:00 Acelists wrote: OK, this is a good reproducible case, I can see it. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1209095/comments/4 On 2012-12-04T20:32:18+00:00 Acelists wrote: So in case of this statusbar scrollbar it is defined in mail/base/content/mailWindowOverlay.xul id="statusbar-progresspanel". The progress is updated in mail/base/content/mailWindow.js::updateProgress . From what I could see we DO NOT call this function often (only once at beginning and once at finish of the progressbar. It is an "undetermined" mode progress bar so it spins by itself once started. It seems the internal XUL implementation of the progressmeter widget is not very efficient. The implementation is in mozilla/toolkit/content/widgets/progressmeter.xml . There seems to be a tight loop calling mozRequestAnimationFrame() without any throttling (if the mozRequestAnimationFrame does not have any). According to http://dvcs.w3.org/hg/webperf/raw- file/tip/specs/RequestAnimationFrame/Overview.html this is the intended operation and the application (FF/TB) determines how many frames per second it generates. So I am not sure what we can do here. Any anybody check if the progressbar in Firefox is also that CPU heavy? Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1209095/comments/5 On 2012-12-04T20:34:22+00:00 Acelists wrote: Moving to Frontend until we determine if this shouldn't actually go into Toolkit. But Security component was way off. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1209095/comments/6 On 2012-12-04T20:42:33+00:00 Bzbarsky wrote: mozRequestAnimationFrame throttles to run no more than at 60Hz. That's its whole purpose. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1209095/comments/7 On 2012-12-04T20:53:50+00:00 Acelists wrote: Is it possible to request even lower framerate? It seems it is quite CPU heavy. The reporter talks 100% of 4-core CPU. But in my testing a tiny progressmeter took 40% of 1 core on a 3Ghz machine. Still a lot. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1209095/comments/8 On 2012-12-04T21:03:10+00:00 Bzbarsky wrote: > Is it possible to request even lower framerate? Not easily, no. However the callee can of course throttle lower by just checking the call time, which is passed to the method... Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1209095/comments/9 On 2012-12-04T22:25:31+00:00 Acelists wrote: Thanks. So I modified the bind
[Desktop-packages] [Bug 1905054] Re: Firefox 83 Breaks WebGL
** Changed in: firefox Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
(In reply to Pat Suwalski from comment #20) > (In reply to Jeff Gilbert [:jgilbert] from comment #19) > > Honestly at this point I'm tending towards #2. > > Websites had the chance to handle this well and they have bungled it, so I > > think we should disable failIfMajorPerformanceCaveat as it stands today. > > Are you suggesting PIXI doesn't handle this properly? Yes, that's what it sounds like. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
Since the status are different for nightly and release, what's the status for beta? For more information, please visit [auto_nag documentation](https://wiki.mozilla.org/Release_Management/autonag#missing_beta_status.py). -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
The system unfortunately does (probably) have a performance caveat, because we've included "readback required for compositing" as a caveat, which is a long-time issue on Linux for us. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
Same problem on a Lenovo T530, i915 grafic controller, using via Firefox 84.0 (Ubuntur 20.04.1 LTS) tensorflow e.g with https://storage.googleapis.com/tfjs-models/demos/posenet/camera.html Just by calling the page it tells (along with poor peformance): Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. canvas_util.ts:83:16 With Chromium browser 87.0.4280.88 , it's works as expected. It worked also nicely with older Firefox Version. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
The goal of the WebGL Working Group was for failIfMajorPerformanceCaveat to allow websites to make better choices about which content to serve to users, ideally via offering a choice to users. I no longer think that this is useful here, or rather it's only ever useful in the very narrow case: When a website does indeed have a fallback ready, and the fallback does actually have better perf. Today this is only true on some Windows systems that have cpu-emulated webgl, but gpu-accelerated canvas2d, but this is not most systems. Simultaneously, we've seen a disappointingly large set of websites break for users that hit the failIfMajorPerformanceCaveat path. Since the usefulness of failIfMajorPerformanceCaveat is very limited, and many sites don't cooperate with us (as the user's User Agent), I think it's best to disable failIfMajorPerformanceCaveat for the time being. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
(In reply to panzi from comment #22) > > Call these bad websites, and try outreach/education > > How do I call Google? Also since they haven't fixed it until now, I doubt > they ever will. Is there some hack to make it work? An user script? That was supposed to be "call out", sorry! Google Maps accepts feedback via the "Send feedback..." menu option. In newer versions of Firefox, the console warning will direct you to use about:config's webgl.disable-fail-if-major-performance-caveat if you keep having issues with bad websites. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
Created attachment 9194895 Bug 1678652 - Disable failIfMajorPerformanceCaveat by default. The goal of the WebGL Working Group was for failIfMajorPerformanceCaveat to allow websites to make better choices about which content to serve to users, ideally via offering a choice to users. I no longer think that this is useful here, or rather it's only ever useful in the very narrow case: When a website does indeed have a fallback ready, and the fallback does actually have better perf. Today this is only true on some Windows systems that have cpu-emulated webgl, but gpu-accelerated canvas2d, but this is not most systems. Simultaneously, we've seen a disappointingly large set of websites break for users that hit the failIfMajorPerformanceCaveat path. Since the usefulness of failIfMajorPerformanceCaveat is very limited, and many sites don't cooperate with us (as the user's User Agent), I think it's best to disable failIfMajorPerformanceCaveat for the time being. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
(In reply to Jeff Gilbert [:jgilbert] from comment #25) > (In reply to panzi from comment #22) > > > Call these bad websites, and try outreach/education > > > > How do I call Google? Also since they haven't fixed it until now, I doubt > > they ever will. Is there some hack to make it work? An user script? > > That was supposed to be "call out", sorry! > Google Maps accepts feedback via the "Send feedback..." menu option. > > In newer versions of Firefox, the console warning will direct you to use > about:config's webgl.disable-fail-if-major-performance-caveat if you keep > having issues with bad websites. Thank you! Finally I have 3D maps in Firefox again! :D -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
https://hg.mozilla.org/mozilla-central/rev/bb634a5d7268 -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
Pushed by jgilb...@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bb634a5d7268 Disable failIfMajorPerformanceCaveat by default. r=lsalzman -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
I can't speak for 3D, but seeing as the 2D rendering is still loads quicker than canvas, the "performance caveat" really isn't. What should PIXI, or any site, do with this information? -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
*** Bug 1684475 has been marked as a duplicate of this bug. *** -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054]
(In reply to Jeff Gilbert [:jgilbert] from comment #24) > (In reply to Pat Suwalski from comment #20) > > (In reply to Jeff Gilbert [:jgilbert] from comment #19) > > > Honestly at this point I'm tending towards #2. > > > Websites had the chance to handle this well and they have bungled it, so > > > I think we should disable failIfMajorPerformanceCaveat as it stands today. > > > > Are you suggesting PIXI doesn't handle this properly? > > Yes, that's what it sounds like. So what changed? If the system in question doesn't have a "major performance caveat" and the browser is reporting that it does, how is that PIXI mishandling it? -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1909886] [NEW] package libcdio-dev 2.0.0-2 failed to install/upgrade: trying to overwrite shared '/usr/include/cdio/cdio_config.h', which is different from other instances of p
Public bug reported: amd64 architecture libcdio-dev installed fine, x86 presented above error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libcdio-dev 2.0.0-2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: libcdio-dev:i386: Install libudf0:i386: Install libudf-dev:i386: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jan 2 15:05:18 2021 DpkgTerminalLog: Preparing to unpack .../libcdio-dev_2.0.0-2_i386.deb ... Unpacking libcdio-dev:i386 (2.0.0-2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libcdio-dev_2.0.0-2_i386.deb (--unpack): trying to overwrite shared '/usr/include/cdio/cdio_config.h', which is different from other instances of package libcdio-dev:i386 ErrorMessage: trying to overwrite shared '/usr/include/cdio/cdio_config.h', which is different from other instances of package libcdio-dev:i386 InstallationDate: Installed on 2020-12-29 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: libcdio Title: package libcdio-dev 2.0.0-2 failed to install/upgrade: trying to overwrite shared '/usr/include/cdio/cdio_config.h', which is different from other instances of package libcdio-dev:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libcdio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1909886 Title: package libcdio-dev 2.0.0-2 failed to install/upgrade: trying to overwrite shared '/usr/include/cdio/cdio_config.h', which is different from other instances of package libcdio-dev:i386 Status in libcdio package in Ubuntu: New Bug description: amd64 architecture libcdio-dev installed fine, x86 presented above error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libcdio-dev 2.0.0-2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: libcdio-dev:i386: Install libudf0:i386: Install libudf-dev:i386: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jan 2 15:05:18 2021 DpkgTerminalLog: Preparing to unpack .../libcdio-dev_2.0.0-2_i386.deb ... Unpacking libcdio-dev:i386 (2.0.0-2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libcdio-dev_2.0.0-2_i386.deb (--unpack): trying to overwrite shared '/usr/include/cdio/cdio_config.h', which is different from other instances of package libcdio-dev:i386 ErrorMessage: trying to overwrite shared '/usr/include/cdio/cdio_config.h', which is different from other instances of package libcdio-dev:i386 InstallationDate: Installed on 2020-12-29 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: libcdio Title: package libcdio-dev 2.0.0-2 failed to install/upgrade: trying to overwrite shared '/usr/include/cdio/cdio_config.h', which is different from other instances of package libcdio-dev:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1909886/+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 1902810] Re: [i915] Dell Latitude 5285 video flicker when an external monitor is connected
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1902810 Title: [i915] Dell Latitude 5285 video flicker when an external monitor is connected Status in xorg-server package in Ubuntu: Expired Bug description: The display on this Dell Latitude 5285 with detachable keyboard flickers when an external monitor is connected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-7625.26~1603389471~20.04~f6b125f-generic 5.8.14 Uname: Linux 5.8.0-7625-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Nov 3 18:38:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a4] InstallationDate: Installed on 2020-07-01 (125 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 8087:0a2b Intel Corp. Bus 001 Device 022: ID 044e:1218 Alps Electric Co., Ltd Alps Touchpad Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5285 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7625-generic root=UUID=f22e0756-4530-44bf-8da3-d0ed47ef183a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 32 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd07/24/2020:br1.10:svnDellInc.:pnLatitude5285:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct32:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5285 dmi.product.sku: 07A4 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1902810/+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 1902721] Re: xrandr fails to set screen size while starting X11
[Expired for x11-xserver-utils (Ubuntu) because there has been no activity for 60 days.] ** Changed in: x11-xserver-utils (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1902721 Title: xrandr fails to set screen size while starting X11 Status in x11-xserver-utils package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: while starting X11 xrandr executes commands: xrandr --newmode "3840x2160_30.00" 338.75 3840 4080 4488 5136 2160 2163 2168 2200 -hsync +vsync xrandr --addmode DP-1 "3840x2160_30.00" xrandr --output DP-1 --mode "3840x2160_30.00" while newmode, addmode work, the third command fails with "xrandr: Configure crtc 0 failed". Looking at all video interfaces, the mode added to DP-1 is there. Now, from some remote shell: DISPLAY=:0.0 xrandr --output DP-1 --mode 3840x2160_30.00 does not fail, but set graphics mode as desired. Trying to pause this to give it more time does not help. Does not work. It works as soon as i log in, set display to ":0.0" and then give the xrandr-command to use and set DP-1 to the desired mode. Removing all xrandr-commands does not help either: the display stays black. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: x11-common 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Nov 3 14:52:24 2020 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: 2018-11-23 16:21:56,549 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1497] InstallationDate: Installed on 2014-01-31 (2468 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: Hewlett-Packard HP Compaq 6200 Pro MT PC PackageArchitecture: all ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-52-generic root=UUID=de4af024-5d59-4f85-b5ca-11f17f085706 ro rootflags=subvol=@ consoleblank=0 video=DP-1:3840x2160M-32@30e SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2018-11-23 (710 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.15 dmi.board.name: 1497 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:svnHewlett-Packard:pnHPCompaq6200ProMTPC:pvr:rvnHewlett-Packard:rn1497:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 6200 Pro MT PC dmi.product.sku: XL504AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1902721/+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 1902660] Re: Display bug
[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1902660 Title: Display bug Status in xserver-xorg-video-intel package in Ubuntu: Expired Bug description: Nor showing display ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-193.224-generic 4.4.236 Uname: Linux 4.4.0-193-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.25 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Nov 3 11:53:40 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21e2] InstallationDate: Installed on 2016-10-13 (1482 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 1143AM1 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-193-generic root=UUID=8cfb78ef-b7c8-4c97-be06-7f457553374b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8HET41WW(1.23) dmi.board.asset.tag: Not Available dmi.board.name: 1143AM1 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:bvr8HET41WW(1.23):bd01/13/2012:svnLENOVO:pn1143AM1:pvrThinkPadE520:rvnLENOVO:rn1143AM1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1143AM1 dmi.product.version: ThinkPad E520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Nov 3 07:54:05 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 739 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1902660/+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 1902715] Re: Change alert sound ubuntu not working (Ubuntu 20.04 LTS)
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1902715 Title: Change alert sound ubuntu not working (Ubuntu 20.04 LTS) Status in gnome-control-center package in Ubuntu: Expired Bug description: I installed the Ubuntu version 20.04 LTS. I would like to change the alert sound. I followed these steps: 1.Open the Activities overview and start typing Sound; 2.Click on Sound to open the panel; 3.In the Alert Sound section, select an alert sound. However, after choosing the preferred sound it does not change! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1902715/+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 1902658] Re: hp printers have version error
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1902658 Title: hp printers have version error Status in hplip package in Ubuntu: Expired Bug description: The version of HPLIP produces many errors. For one, it produces many on bug 1899360 (not sure of the bug number), in association with MASSIVE errors in basic packages. It produces many on the bug 1902949. The issue is one affecting several packages (1899360) on upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1902658/+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 1902721] Re: xrandr fails to set screen size while starting X11
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1902721 Title: xrandr fails to set screen size while starting X11 Status in x11-xserver-utils package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: while starting X11 xrandr executes commands: xrandr --newmode "3840x2160_30.00" 338.75 3840 4080 4488 5136 2160 2163 2168 2200 -hsync +vsync xrandr --addmode DP-1 "3840x2160_30.00" xrandr --output DP-1 --mode "3840x2160_30.00" while newmode, addmode work, the third command fails with "xrandr: Configure crtc 0 failed". Looking at all video interfaces, the mode added to DP-1 is there. Now, from some remote shell: DISPLAY=:0.0 xrandr --output DP-1 --mode 3840x2160_30.00 does not fail, but set graphics mode as desired. Trying to pause this to give it more time does not help. Does not work. It works as soon as i log in, set display to ":0.0" and then give the xrandr-command to use and set DP-1 to the desired mode. Removing all xrandr-commands does not help either: the display stays black. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: x11-common 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Nov 3 14:52:24 2020 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: 2018-11-23 16:21:56,549 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1497] InstallationDate: Installed on 2014-01-31 (2468 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: Hewlett-Packard HP Compaq 6200 Pro MT PC PackageArchitecture: all ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-52-generic root=UUID=de4af024-5d59-4f85-b5ca-11f17f085706 ro rootflags=subvol=@ consoleblank=0 video=DP-1:3840x2160M-32@30e SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2018-11-23 (710 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.15 dmi.board.name: 1497 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:svnHewlett-Packard:pnHPCompaq6200ProMTPC:pvr:rvnHewlett-Packard:rn1497:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 6200 Pro MT PC dmi.product.sku: XL504AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1902721/+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 1902545] Re: software-properties-gtk error
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1902545 Title: software-properties-gtk error Status in software-properties package in Ubuntu: Expired Bug description: ERROR:dbus.proxies:Introspect error on :1.225:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 211, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.225 was not provided by any .service files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1902545/+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 1902446] Re: Not possible to see list of wifi networks
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1902446 Title: Not possible to see list of wifi networks Status in network-manager package in Ubuntu: Expired Bug description: Using the default 'light' theme, the network listing is impossible to read ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 19:41:38 2020 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-15 (1355 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902446/+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 1898389] Re: browser frequently crashing with trap int3
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1898389 Title: browser frequently crashing with trap int3 Status in chromium-browser package in Ubuntu: Expired Bug description: I used to be able to have many tabs open with Chromium without problems. Lately it crashes or gives "aw snap" errors (see kernel messages below) if I start to keep more than 25 or so open. Description:Ubuntu 16.04.7 LTS Release:16.04 chromium-browser: Installed: 85.0.4183.83-0ubuntu0.16.04.2 Candidate: 85.0.4183.121-0ubuntu0.16.04.1 Version table: 85.0.4183.121-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages *** 85.0.4183.83-0ubuntu0.16.04.2 100 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 18.0.1025.151~r130497-0ubuntu1 500 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages dmesg: [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be sp:7ffdfc31ca40 error:0 [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 sp:7ffdfc31ca70 error:0 [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 sp:7ffd8fc04770 error:0 [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 sp:7ffdfc31b2c0 error:0 [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be sp:7ffdfc31bd40 error:0 [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 sp:7ffdfc31cab0 error:0 [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 sp:7ffdfc31b300 error:0 [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 sp:7ffdfc31c640 error:0 [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be sp:7ffdfc31a6a0 error:0 [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be sp:7ffdfc31ca40 error:0 [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 sp:7fe1dcaf95e0 error:0 [519367.329864] traps: chromium-browse[24588] trap invalid opcode ip:558478cb1962 sp:7ffdfc31cb68 error:0 in chromium-browser[558471f1c000+a1c4000] [519367.357674] traps: chromium-browse[24558] trap invalid opcode ip:558478cb1962 sp:7ffdfc31b6a8 error:0 in chromium-browser[558471f1c000+a1c4000] [519367.454722] traps: chromium-browse[24483] trap int3 ip:5584761d6817 sp:7ffdfc316260 error:0 [519372.392415] traps: chromium-browse[24372] trap int3 ip:558475879bc2 sp:7ffdfc31abd0 error:0 [519372.493260] traps: chromium-browse[24606] trap int3 ip:5584758743be sp:7ffdfc31bbb0 error:0 [519429.551779] traps: chromium-browse[24895] trap int3 ip:558476229df7 sp:7ffdfc31d020 error:0 [519429.585427] traps: chromium-browse[24884] trap int3 ip:5584761d6817 sp:7ffdfc3165c0 error:0 [519429.588811] traps: chromium-browse[24697] trap int3 ip:5584761d6817 sp:7ffdfc3164c0 error:0 [519429.646931] traps: chromium-browse[24742] trap int3 ip:5584761d6817 sp:7ffdfc31c5b0 error:0 [519429.841404] traps: chromium-browse[24906] trap invalid opcode ip:558478cb1962 sp:7ffdfc31cb68 error:0 in chromium-browser[558471f1c000+a1c4000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+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 1883292] Re: Laptop not suspending on lid close after external monitors disconnected
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1883292 Title: Laptop not suspending on lid close after external monitors disconnected Status in gdm3 package in Ubuntu: Expired Bug description: I have a Dell XPS 13 9380 laptop with Type-C dock. There are two external monitors (DisplayPort) and USB mouse attached to the doc. Normally I disconnect the dock cable from the laptop, close the laptop lid and laptop suspends. However, sometimes it doesn't suspend. I can see the 'Lid closed.' message in systemd-logind log which is normally followed by a sleep. Once this happens, laptop no longer suspends on lid close until I restart Gnome session. Also, if I lock it, the screen goes black but the backlight does not turn off. I can put computer to a sleep from Gnome menu. I'm not sure if it's issue is specific to Type-C dock though. It happens rarely, maybe 1 of 20 times. It appears like gsd does not detect monitors disconnect event in some cases: abram@abram-laptop:~$ systemd-inhibit --list --mode=block WHO UID USER PID COMM WHAT WHY MODE gdm 123 gdm 1977595 gsd-power handle-lid-switch External monitor attached or configuration changed recently block gdm 123 gdm 1977593 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses block abram 1000 abram 779130 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses block 3 inhibitors listed. I've also seen a similar issue mentioned at askubuntu: https://askubuntu.com/questions/1196871/gnome-supend-on-laptop-lid-close-no-longer-works-since-19-10-upgrade The accepted answer involves killing gsd-power but that's more like a workaround than a fix; the same presumably happens when Gnome session is restarted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jun 12 19:19:35 2020 InstallationDate: Installed on 2019-04-17 (421 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to focal on 2020-04-02 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1883292/+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 1667992] Re: ctrl-c sometimes causes wayland session to exit
[Expired for gnome-session (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1667992 Title: ctrl-c sometimes causes wayland session to exit Status in gnome-session package in Ubuntu: Expired Bug description: Ubuntu 16.10; gnome-session 3.20.2-1ubuntu7; Gnome on Wayland. Ctrl-C should copy text; sometimes instead kills Gnome session. Sometimes, when I try to copy, I get logged out (presumably due to this combination being interpreted as SIGINT by Gnome). Unfortunately, I'm having trouble reliably reproducing this bug. It doesn't seem to happen if one copy has been done already (can't confirm though), however I can successfully copy immediately after logging in again. Even then, though, it doesn't always happen after first login, and many days it never happens at all. I don't even know if it happens when any application is focused (mostly because I only really use Chrome and the terminal in day-to- day operation), though I note that it's never happened when I've used that combination to interrupt another program under Gnome Terminal (not to say it can't happen though, I don't do that very often). Due to the difficulty in reproducing, I've yet to determine if it's even specifically a part of this package (though it seems a good place to start). I'll try remember to provide updates if I notice any other behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1667992/+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
