[Desktop-packages] [Bug 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/
@Olivier Ah, sorry, thank you for explaining this. This isn't what I
want to do, I was just trying to strip back to the basics of what
https://www.chromium.org/administrators/linux-quick-start said to do and
demonstrate that it wasn't working.
I changed my policy so it says
{
"RestoreOnStartupURLs": "www.chromium.org"
}
Now when I open chromium, it doesn't go to www.chromium.org. When I go to
chrome://policy it reports RestoreOnStartupURLs has value www.chromium.org but
says there is an error "Expected list value". I changed it to
{
"RestoreOnStartupURLs": ["www.chromium.org"]
}
And it works. It is a shame the example code given on
https://www.chromium.org/administrators/linux-quick-start doesn't function any
more.
What got me to this point was trying to set
{
"EnableMediaRouter": false
}
to stop chromium from monitoring network ports. Previously I couldn't get
chromium to acknowledge a policy is set, but now I see I am able to set policy,
but this one is not enforced. Still, I think this is a different problem to
this thread. Thanks again!
--
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/1714244
Title:
[snap] apparmor denials on /etc/chromium-browser/policies/
Status in chromium-browser package in Ubuntu:
Fix Committed
Bug description:
[1565519.440403] audit: type=1400 audit(1504185084.568:68574811):
apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
name="/etc/chromium-browser/policies/managed/" pid=19433 comm
="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
[1565519.440527] audit: type=1400 audit(1504185084.568:68574812):
apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
name="/etc/chromium-browser/policies/recommended/" pid=19433 comm
="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Those denials don't appear to prevent the app from running. Still,
they should be investigated and fixed if possible.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+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 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow
Please run these commands: ls -l /dev/dri/* > dri.txt glxinfo > glx.txt and attach the resulting text files here. -- 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/1902652 Title: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow Status in mesa package in Ubuntu: Incomplete Status in xf86-video-armsoc package in Ubuntu: Incomplete Bug description: 3d rendering is very slow, also when surfing the internet, webpages take a while to render. Internet access is not the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.64+ aarch64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Nov 3 05:42:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci: ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Allwinner sun4i DRM driver" Driver "armsoc" Option "DRI2" "true" EndSection version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902652/+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 1791981] Re: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
*** This bug is a duplicate of bug 1897530 *** https://bugs.launchpad.net/bugs/1897530 ** This bug has been marked a duplicate of bug 1897530 The modesetting driver does not gracefully handle missing connectors on EnterVT -- 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/1791981 Title: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in Nvidia: New Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu Release: Ubuntu 18.04.1 LTS Package version: xserver-xorg: 1:7.7+19ubuntu7.1 When my laptop resumes after suspend, the desktop session crashes and a new one is started. So each time I lose all open applications and unsaved data! The expected behavior would be obviously to restore the suspended session. I had a look through log files and found that Xorg.0.log ends with the following error lines: [ 6004.019] (II) NVIDIA(0): Setting mode "NULL" [ 6004.026] (EE) modeset(G0): failed to set mode: No space left on device [ 6004.026] (EE) Fatal server error: [ 6004.026] (EE) EnterVT failed for gpu screen 0 [ 6004.027] (EE) [ 6004.027] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 6004.027] (EE) [ 6004.065] (EE) Server terminated with error (1). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1791981/+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 1897530] Re: The modesetting driver does not gracefully handle missing connectors on EnterVT
Bug 1857443 appears to be a duplicate of bug 1791981, so this should also have been a duplicate of bug 1791981... However since this bug is more advanced we can keep tracking it here. -- 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/1897530 Title: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Invalid Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in xorg-server source package in Focal: Confirmed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Bug description: [Impact] On a hybrid machine where NVIDIA is rendering the screen, if a display attached to a dock is removed while on suspend mode, on resume X crashes. [Test case] Test hot-unplug during suspend and resume, X shouldn't crash. [Regression potential] This replaces a patch we had with two commits that got merged upstream after a fairly extensive review process: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/ And we ship it in groovy. If there were issues caused by it, they would be around hot-unplugging a dock while on suspend and such. -- Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1901695] Re: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary
*** This bug is a duplicate of bug 1897530 ***
https://bugs.launchpad.net/bugs/1897530
** This bug is no longer a duplicate of bug 1791981
[nvidia] X Server session crash with "No space left on device" and then
"EnterVT failed for gpu screen 0"
** This bug has been marked a duplicate of bug 1897530
The modesetting driver does not gracefully handle missing connectors on
EnterVT
--
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/1901695
Title:
Ubuntu 20.04 Suspend resume fails if laptop lid is closed
[modeset(G0): failed to set mode: No space left on device] (Razer
Blade 15 laptop with nvidia proprietary driver)
Status in xorg-server package in Ubuntu:
New
Bug description:
Steps to reproduce:
- Boot docked laptop (i.e. lid closed, external monitors connected, USB
keyboard plugged in)
- Log in, click desktop menu item "Power off / logout -> suspend"
- Laptop will suspend
- Press key on USB keyboard to resume
- Resume fails - external monitor shows black screen with cursor
- (this used to work ok in Ubuntu 18.04)
Journal shows that Xorg failed:
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-0): connected
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-0): Internal TMDS
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-0): 165.0 MHz maximum pixel clock
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DFP-1: disconnected
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DFP-1: Internal DisplayPort
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DFP-1: 1440.0 MHz maximum pixel clock
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-2): connected
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-2): Internal TMDS
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-2): 165.0 MHz maximum pixel clock
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (II) NVIDIA(0):
Setting mode "HDMI-0: nvidia-auto-select @1050x1680 +2102+0
{ViewPortIn=1050x1680, ViewPortOut=1680x1050+0+0, Rotation=90}, DP-1:
nvidia-auto-select @1050x1680 +1050+0 {ViewPortIn=1050x1680,
ViewPortOut=1680x1050+0+0, Rotation=90}"
...
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) modeset(G0):
failed to set mode: No space left on device
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE)
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Fatal server error:
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) EnterVT failed
for gpu screen 0
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE)
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE)
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Please consult the
The X.Org Foundation support
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: at
http://wiki.x.org
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: for help.
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Please also
check the log file at "/var/log/Xorg.0.log" for additional information.
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE)
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Server
terminated with error (1). Closing log file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+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 1897530] Re: The modesetting driver does not gracefully handle missing connectors on EnterVT
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: New => Confirmed -- 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/1897530 Title: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Invalid Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in xorg-server source package in Focal: Confirmed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Bug description: [Impact] On a hybrid machine where NVIDIA is rendering the screen, if a display attached to a dock is removed while on suspend mode, on resume X crashes. [Test case] Test hot-unplug during suspend and resume, X shouldn't crash. [Regression potential] This replaces a patch we had with two commits that got merged upstream after a fairly extensive review process: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/ And we ship it in groovy. If there were issues caused by it, they would be around hot-unplugging a dock while on suspend and such. -- Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1897530] Re: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
** Summary changed: - The modesetting driver does not gracefully handle missing connectors on EnterVT + [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" ** Summary changed: - [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" + [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" ** Tags added: nvidia ** Tags added: focal -- 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/1897530 Title: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Invalid Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in xorg-server source package in Focal: Confirmed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Bug description: [Impact] On a hybrid machine where NVIDIA is rendering the screen, if a display attached to a dock is removed while on suspend mode, on resume X crashes. [Test case] Test hot-unplug during suspend and resume, X shouldn't crash. [Regression potential] This replaces a patch we had with two commits that got merged upstream after a fairly extensive review process: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/ And we ship it in groovy. If there were issues caused by it, they would be around hot-unplugging a dock while on suspend and such. -- Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1897530] Re: The modesetting driver does not gracefully handle missing connectors on EnterVT
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu Focal) Status: New => Confirmed -- 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/1897530 Title: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Invalid Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in xorg-server source package in Focal: Confirmed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Bug description: [Impact] On a hybrid machine where NVIDIA is rendering the screen, if a display attached to a dock is removed while on suspend mode, on resume X crashes. [Test case] Test hot-unplug during suspend and resume, X shouldn't crash. [Regression potential] This replaces a patch we had with two commits that got merged upstream after a fairly extensive review process: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/ And we ship it in groovy. If there were issues caused by it, they would be around hot-unplugging a dock while on suspend and such. -- Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow
This iso won't install. On Tue, Nov 3, 2020 at 8:35 PM Daniel van Vugt <1902...@bugs.launchpad.net> wrote: > Please run these commands: > > ls -l /dev/dri/* > dri.txt > glxinfo > glx.txt > > and attach the resulting text files here. > > ** Changed in: mesa (Ubuntu) >Status: New => Incomplete > > ** Changed in: xf86-video-armsoc (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1902652 > > Title: > [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow > > Status in mesa package in Ubuntu: > Incomplete > Status in xf86-video-armsoc package in Ubuntu: > Incomplete > > Bug description: > 3d rendering is very slow, also when surfing the internet, webpages > take a while to render. Internet access is not the problem. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > Uname: Linux 4.19.64+ aarch64 > ApportVersion: 2.20.9-0ubuntu7.18 > Architecture: arm64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: XFCE > Date: Tue Nov 3 05:42:00 2020 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: > > Lspci: > > ProcEnviron: >LANGUAGE=en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ > root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ > noquiet splash vt.handoff=1 > Renderer: Software > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > XorgConf: >Section "Device" > Identifier "Allwinner sun4i DRM driver" > Driver "armsoc" > Option "DRI2" "true" >EndSection > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902652/+subscriptions > -- 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/1902652 Title: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow Status in mesa package in Ubuntu: Incomplete Status in xf86-video-armsoc package in Ubuntu: Incomplete Bug description: 3d rendering is very slow, also when surfing the internet, webpages take a while to render. Internet access is not the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.64+ aarch64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Nov 3 05:42:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci: ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Allwinner sun4i DRM driver" Driver "armsoc" Option "DRI2" "true" EndSection version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notificatio
[Desktop-packages] [Bug 1065126]
*** Bug 1668182 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/1065126 Title: "Always do this from now on" does not work Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Downloading an unknown file type in Firefox displays a dialog for choosing which application to use for opening the file. The dialog contains a check box labelled "Always do this action from now on". Checking this option does not work: When I download a file of the same type next time, the same dialog is displayed again. This feature is broken for as long as I can remember (> 10 years). It's time it was fixed (or removed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruediger 2536 F pulseaudio BuildID: 20120907231657 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20bb,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Channel: Unavailable Date: Wed Oct 10 18:17:44 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 172.31.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 172.31.0.0/20 dev wlan0 proto kernel scope link src 172.31.9.26 metric 2 MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.2 totem-mozilla 3.0.1-0ubuntu21.1 icedtea-6-plugin 1.2-2ubuntu1.2 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago) dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 6457BBG 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:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6457BBG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1065126/+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 1846423]
I'm also affected by this, happy to provide help in debugging it. -- 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/1846423 Title: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Cannot dismiss reminders for a recurrence with exceptions. Calendar entries like this are generated: BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:My recurrence TRIGGER;VALUE=DURATION:-PT120M X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE parame ter with an illegal type for property: VALUE=DURATION END:VALARM ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xul-ext-lightning 1:60.8.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vectro 2004 F pulseaudio /dev/snd/controlC0: vectro 2004 F pulseaudio BuildID: 20190705212852 Channel: Unavailable CurrentDesktop: KDE Date: Wed Oct 2 17:50:39 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.14 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705212852 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L78 Ver. 01.43 dmi.board.name: 2101 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.3C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 640 G1 dmi.product.sku: T4M40UT#ABA dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1846423/+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 1847247]
Thanks Created new bug 1674520 -- 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/1847247 Title: External dictionaries are not loaded Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Fix Released Status in thunderbird source package in Eoan: Fix Released Bug description: On Ubuntu Eoan and most recent Thunderbird, the external Hunspell dictionaries are not available anymore on Thunderbird for spellcheck. The symlink is still in place: lrwxrwxrwx 1 root root20 dec 15 2017 dictionaries -> ../../share/hunspell But data doesn't get loaded for some reason. NOTE TO SRU TEAM: Please do not release this package without consulting first. This is a security update pushed via -proposed to get a bit more testing. Will be released via it's own processes. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847247/+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 1847247]
@crxssi: I suggest opening a new bug report. The issue discussed here was closed as resolved, it would be better to start a new conversation in a separate bug report. -- 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/1847247 Title: External dictionaries are not loaded Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Fix Released Status in thunderbird source package in Eoan: Fix Released Bug description: On Ubuntu Eoan and most recent Thunderbird, the external Hunspell dictionaries are not available anymore on Thunderbird for spellcheck. The symlink is still in place: lrwxrwxrwx 1 root root20 dec 15 2017 dictionaries -> ../../share/hunspell But data doesn't get loaded for some reason. NOTE TO SRU TEAM: Please do not release this package without consulting first. This is a security update pushed via -proposed to get a bit more testing. Will be released via it's own processes. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847247/+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 1846423]
Can confirm this still occurs in TB78.3.1. -- 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/1846423 Title: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Cannot dismiss reminders for a recurrence with exceptions. Calendar entries like this are generated: BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:My recurrence TRIGGER;VALUE=DURATION:-PT120M X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE parame ter with an illegal type for property: VALUE=DURATION END:VALARM ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xul-ext-lightning 1:60.8.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vectro 2004 F pulseaudio /dev/snd/controlC0: vectro 2004 F pulseaudio BuildID: 20190705212852 Channel: Unavailable CurrentDesktop: KDE Date: Wed Oct 2 17:50:39 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.14 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705212852 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L78 Ver. 01.43 dmi.board.name: 2101 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.3C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 640 G1 dmi.product.sku: T4M40UT#ABA dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1846423/+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 1897530] Re: The modesetting driver does not gracefully handle missing connectors on EnterVT
Original bug: https://bugs.launchpad.net/somerville/+bug/1857443 -- 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/1897530 Title: The modesetting driver does not gracefully handle missing connectors on EnterVT Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Invalid Status in xorg-server-hwe-18.04 source package in Bionic: New Status in xorg-server source package in Focal: New Status in xorg-server-hwe-18.04 source package in Focal: Invalid Bug description: [Impact] On a hybrid machine where NVIDIA is rendering the screen, if a display attached to a dock is removed while on suspend mode, on resume X crashes. [Test case] Test hot-unplug during suspend and resume, X shouldn't crash. [Regression potential] This replaces a patch we had with two commits that got merged upstream after a fairly extensive review process: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/ And we ship it in groovy. If there were issues caused by it, they would be around hot-unplugging a dock while on suspend and such. -- Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1789758] Re: bluetooth headphones a2dp profile does not function after suspend, only HSP
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1789758 Title: bluetooth headphones a2dp profile does not function after suspend, only HSP Status in pulseaudio package in Ubuntu: Expired Bug description: 1) lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 2) $ apt-cache policy bluez bluez: Installed: 5.48-0ubuntu3.1 Candidate: 5.48-0ubuntu3.1 Version table: *** 5.48-0ubuntu3.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.48-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) bluetooth headphones stay working in a2dp mode even after suspend 4) bluetooth headphones connect but no sound will come out of a2dp mode, only in HSP profile ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 29 18:07:26 2018 InstallationDate: Installed on 2018-05-26 (95 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180525) InterestingModules: rfcomm bnep btusb bluetooth ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9e84ffd4-d629-4dcd-a6c4-6648d1a34665 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0041.2015.0316.1442 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-406 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0041.2015.0316.1442:bd03/16/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-406:cvn:ct3:cvr: dmi.product.family: To be filled by O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: 48:51:B7:07:93:F5 ACL MTU: 1021:5 SCO MTU: 96:5 DOWN RX bytes:5617087 acl:790 sco:22622 events:634625 errors:0 TX bytes:540631745 acl:632348 sco:22584 commands:537 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1789758/+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 1894225] Re: Blocked UI and 100% cpu in gnome-shell when selecting text
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1894225 Title: Blocked UI and 100% cpu in gnome-shell when selecting text Status in gnome-shell package in Ubuntu: Expired Bug description: After upgrading from ubuntu-18.04 to 20.04 I noticed that selecting text via shift-rightarrow in any app (gedit, chrome, firefox) makes X11 stop updating all apps' window contents while gnome-shell jumps to 100% cpu in top. This is on an idle DELL e7440 laptop (i5-4210U with 8 GB of RAM) and a fresh ubuntu install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 15:44:00 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-08-26 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894225/+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 1893774] Re: [amdgpu] Screen freeze when loging in after a log out
[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1893774 Title: [amdgpu] Screen freeze when loging in after a log out Status in linux package in Ubuntu: Expired Status in xserver-xorg-video-amdgpu package in Ubuntu: Expired Bug description: I use Kubuntu 20.04.1 on Thinpad T495 with encrypted disk (LVMS) and finger print reader. PROBLEM: 1. I boot the laptop and can work 2. I log my user out and try to log in again with te password 3. I enter the password and press enter 4. The screen freezes and shows the login screen. It can only be killed and rebooted. Also, the finger print reader works everywhere, but not in the situation above. These are the seetings of my common-auth file: # here are the per-package modules (the "Primary" block) auth [success=2 default=ignore] pam_fprintd.so max_tries=1 timeout=10 # debug auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass But I do NOT think that the problem is related to the fingerprint reader. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Tue Sep 1 13:38:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-08-31 (0 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 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.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 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.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.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893774/+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 1893774] Re: [amdgpu] Screen freeze when loging in after a log out
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1893774 Title: [amdgpu] Screen freeze when loging in after a log out Status in linux package in Ubuntu: Expired Status in xserver-xorg-video-amdgpu package in Ubuntu: Expired Bug description: I use Kubuntu 20.04.1 on Thinpad T495 with encrypted disk (LVMS) and finger print reader. PROBLEM: 1. I boot the laptop and can work 2. I log my user out and try to log in again with te password 3. I enter the password and press enter 4. The screen freezes and shows the login screen. It can only be killed and rebooted. Also, the finger print reader works everywhere, but not in the situation above. These are the seetings of my common-auth file: # here are the per-package modules (the "Primary" block) auth [success=2 default=ignore] pam_fprintd.so max_tries=1 timeout=10 # debug auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass But I do NOT think that the problem is related to the fingerprint reader. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Tue Sep 1 13:38:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-08-31 (0 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 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.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 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.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.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893774/+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 1894415] Re: XORG crashes with segfault on Ubuntu 1804 during login
[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/1894415 Title: XORG crashes with segfault on Ubuntu 1804 during login Status in xorg-server package in Ubuntu: Expired Bug description: This is maybe a long shot, but I have a Dell XPS 13 2020 running Ubuntu 18.04. It was running fine for a while, but for some reason it recently developed an issue where xorg crashes on login. I get as far as the desktop, but then it locks up and mouse/keyboard stop responding. I have verified this happens if I select the following login shells: Ubuntu, Gnome Classic, xfce4. It does not happen under wayland, so I have switched to that for now. The segfault is as follows: Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) Backtrace: Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x55e34e1bba9d] Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) 1: /usr/lib/xorg/Xorg (0x55e34e003000+0x1bc839) [0x55e34e1bf839] Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f3e4ca86000+0x128a0) [0x7f3e4ca988a0] Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) 3: /usr/lib/xorg/Xorg (DRI2CloseScreen+0x33) [0x55e34e18fc43] Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) 4: /usr/lib/xorg/modules/drivers/modesetting_drv.so (0x7f3e49b5d000+0x7d48) [0x7f3e49b64d48] Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) 5: /usr/lib/xorg/Xorg (0x55e34e003000+0xc6407) [0x55e34e0c9407] Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) 6: /usr/lib/xorg/Xorg (0x55e34e003000+0x137762) [0x55e34e13a762] Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) 7: /usr/lib/xorg/Xorg (0x55e34e003000+0xe4bf0) [0x55e34e0e7bf0] Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) 8: /usr/lib/xorg/Xorg (0x55e34e003000+0x57000) [0x55e34e05a000] Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7f3e4c6b6b97] Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) 10: /usr/lib/xorg/Xorg (_start+0x2a) [0x55e34e043b8a] Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) Segmentation fault at address 0x90 Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: Fatal server error: Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) Caught signal 11 (Segmentation fault). Server aborting Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: Please consult the The X.Org Foundation support Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: at http://wiki.x.org Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: for help. Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) Please also check the log file at "/home//.local/share/xorg/Xorg.0.log" for additional information. Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (EE) Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error Sep 05 21:32:18 -xps /usr/lib/gdm3/gdm-x-session[1902]: (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error I have attached the Xorg log file, if that is helpful. Are there any steps I can take to debug? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1894415/+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 1876706] Re: TILEd monitor not getting full res
** Package changed: mutter (Ubuntu) => linux (Ubuntu) ** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/-/issues/27 Importance: Unknown Status: Unknown ** Summary changed: - TILEd monitor not getting full res + [i915] TILEd monitor not getting full res -- 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/1876706 Title: [i915] TILEd monitor not getting full res Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I have an LG 34WK95U monitor which appears to be tiled using two diplay port interfaces connect over thunderbolt. I'm unable to get ubuntu to drive the monitor at it's full 5120x2160@60 resolution. Manually I can force it to 5120x2160@30, but by default Ubuntu gives me 3440x1440@60. I've been researching what the problem might be, my findings so far are collected in these two questions on askubuntu https://askubuntu.com/questions/1233284/tiled-monitor-support-lg-34wk95u https://askubuntu.com/questions/1230124/high-res-monitor-support-5120x2160-lg-34wk95 I've tried switching my laptop gpu from NVidia to the built-in Intel, but the problem persists. The monitor worked in Windows before I wiped the laptop to install Ubuntu. So I'm stuck with the conclusion that there is a bug somewhere at a lower layer preventing this from working since none of the things I've tested have worked. Ideally this should of course have worked out of the box as on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-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: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 4 12:33:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0906] Subsystem: Dell TU117GLM [Quadro T2000 Mobile / Max-Q] [1028:0906] InstallationDate: Installed on 2020-04-24 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5540 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0FMYX6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/25/2019:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn0FMYX6:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5540 dmi.product.sku: 0906 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.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-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1876706/+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 1903211] Re: Computer freezes randomly after unsuspending
** Package changed: ubuntu => xserver-xorg-video-nouveau (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1903211 Title: Computer freezes randomly after unsuspending Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: After unsuspending Ubuntu 20.04 the PC feezes for long periods of time. A look at HTOP shows a CPU core locking (i have 8 cores), and the command /var/log/syslog indicates that there is excessive logging happening...like hundreds of logs per second. I have tried blacklisting the nouveau driver and installing NVIDIA but that caused other problems in that my PC could not boot up, presumably due to incorrect NVIDIA settings. So now i just make sure the PC does not suspend, and when it does i have to restart to use the PC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1903211/+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 1903211] [NEW] Computer freezes randomly after unsuspending
You have been subscribed to a public bug: After unsuspending Ubuntu 20.04 the PC feezes for long periods of time. A look at HTOP shows a CPU core locking (i have 8 cores), and the command /var/log/syslog indicates that there is excessive logging happening...like hundreds of logs per second. I have tried blacklisting the nouveau driver and installing NVIDIA but that caused other problems in that my PC could not boot up, presumably due to incorrect NVIDIA settings. So now i just make sure the PC does not suspend, and when it does i have to restart to use the PC. ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Computer freezes randomly after unsuspending https://bugs.launchpad.net/bugs/1903211 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903200] Re: Ubuntu is unable to detect one of my GPUs
It looks like there are two problems here: 1. The kernel can't find the GPU at all. This is either due to a BIOS setting or some kind of optimus / prime switch you need to flip (sorry I'm not familiar with that). 2. You tried to manually install unsupported driver version 455.23.05 and it failed. So first please check your BIOS and make sure the discrete GPU is enabled. If that doesn't fix it then some quick googling suggests the problem should be fixed by installing a working driver, so try: sudo apt update sudo apt install --reinstall nvidia-driver-450 nvidia-prime ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1903200 Title: Ubuntu is unable to detect one of my GPUs Status in Ubuntu: Incomplete Bug description: I have an MSI laptop which was working fine with Ubuntu 18, but I decided to upgrade. It has one of these dual graphics setups, which and Intel HD 630 and a NVIDIA GTX 1060 6GB. On Ubuntu 18, I simply get the NVIDIA GPU to work by selecting its drivers on the "Additional Drivers" tab under "Software and Updates", but on this version of Ubuntu, my GPU doesn't appear there any more. Also, if I type this in the console: $ lspci | grep -i --color 'vga\|3d\|2d' This is the only line I get: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) Just in case, my laptop model is this: https://es.msi.com/Laptop /GL72VR-7RFX I also have Windows on dual boot and the GPU works perfectly fine there. Also, it is not disabled on the BIOS or something like that. I don't think that is even possible on my BIOS either. $ lspci -k | grep -EA3 'VGA|3D|Display' 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) DeviceName: Onboard IGD Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 630 Kernel driver in use: i915 $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA Controller [AHCI Mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) 00:1c.3 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #4 (rev f1) 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1f.0 ISA bridge: Intel Corporation HM175 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 02:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) 03:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10) 04:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller Looking at the output, I don't know why it says that my processor is an Intel Xeon... it's actually a i7-7700HQ. Here is a thread on the forum with more people experiencing this issue: https://ubuntuforums.org/showthread.php?t=2443007 Any help would be appreciated. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 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.10 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 5 20:18:37 2020 DistUpgraded: 2020-05-08 15:27:01,107 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 45
Re: [Desktop-packages] [Bug 1903176] Re: Ubuntu crashes many times and go to login screen while browosing site in firefox version -82
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1903176 Title: Ubuntu crashes many times and go to login screen while browosing site in firefox version -82 Status in ubuntu-meta package in Ubuntu: New Bug description: I have upgraded from Ubuntu 20.04 to 20.10 recently and I have noticed that while browsing sites in Firefox especially using Youtube in Firefox, the System crashes and go to Login screen. all the application used are closed and need to reopen again. I am using 4 GB RAM 64 Bit Ubuntu. Kindly fix. Thank You so much - Arise ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.12 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Nov 5 23:52:18 2020 InstallationDate: Installed on 2017-10-04 (1127 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-24 (11 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1903176/+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 1902969] Re: desktop freezes when changing thundebird win decorations
After the freeze happens next, please wait 10 seconds, reboot and then run: journalctl -b-1 > prevboot.txt gsettings list-recursively org.gnome.shell > settings.txt and attach the resulting text files here. -- 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/1902969 Title: desktop freezes when changing thundebird win decorations Status in gnome-shell package in Ubuntu: Incomplete Bug description: I noticed a bug. In Thunderbird (deb or snap) version open and right click on the tab bar and choose customization and mess around with showing title or not and close out of it the icon for TB is still in the dock. If you click on the icon it locks up the UI. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.3.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mram 2160 F pulseaudio /dev/snd/controlC0: mram 2160 F pulseaudio BuildID: 20201006011220 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 18:55:14 2020 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-10-04 (31 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.45 metric 100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.0/20200629202523 (Out of date) Profile0 (Default) - LastVersion=78.3.2/20201006011220 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.release: 4.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AGH6120H.86A.0015.2012.0926.1822 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61AGL dmi.board.vendor: Intel Corporation dmi.board.version: G71256-202 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: sabc1 dmi.modalias: dmi:bvnIntelCorp.:bvrAGH6120H.86A.0015.2012.0926.1822:bd09/26/2012:br4.6:svnSystem76,Inc.:pnSableComplete:pvrsabc1:rvnIntelCorporation:rnDH61AGL:rvrG71256-202:cvnSystem76,Inc.:ct3:cvrsabc1: dmi.product.family: To be filled by O.E.M. dmi.product.name: Sable Complete dmi.product.sku: To be filled by O.E.M. dmi.product.version: sabc1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902969/+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 1902969] Re: desktop freezes when changing thundebird win decorations
Please run the following commands: journalctl -b0 > journal.txt gsettings list-recursively org.gnome.shell > settings.txt and then attach the resulting text files here. -- 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/1902969 Title: desktop freezes when changing thundebird win decorations Status in gnome-shell package in Ubuntu: Incomplete Bug description: I noticed a bug. In Thunderbird (deb or snap) version open and right click on the tab bar and choose customization and mess around with showing title or not and close out of it the icon for TB is still in the dock. If you click on the icon it locks up the UI. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.3.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mram 2160 F pulseaudio /dev/snd/controlC0: mram 2160 F pulseaudio BuildID: 20201006011220 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 18:55:14 2020 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-10-04 (31 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.45 metric 100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.0/20200629202523 (Out of date) Profile0 (Default) - LastVersion=78.3.2/20201006011220 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.release: 4.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AGH6120H.86A.0015.2012.0926.1822 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61AGL dmi.board.vendor: Intel Corporation dmi.board.version: G71256-202 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: sabc1 dmi.modalias: dmi:bvnIntelCorp.:bvrAGH6120H.86A.0015.2012.0926.1822:bd09/26/2012:br4.6:svnSystem76,Inc.:pnSableComplete:pvrsabc1:rvnIntelCorporation:rnDH61AGL:rvrG71256-202:cvnSystem76,Inc.:ct3:cvrsabc1: dmi.product.family: To be filled by O.E.M. dmi.product.name: Sable Complete dmi.product.sku: To be filled by O.E.M. dmi.product.version: sabc1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902969/+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 1902969] Re: desktop freezes when changing thundebird win decorations
Also... Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1902969 Title: desktop freezes when changing thundebird win decorations Status in gnome-shell package in Ubuntu: Incomplete Bug description: I noticed a bug. In Thunderbird (deb or snap) version open and right click on the tab bar and choose customization and mess around with showing title or not and close out of it the icon for TB is still in the dock. If you click on the icon it locks up the UI. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.3.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mram 2160 F pulseaudio /dev/snd/controlC0: mram 2160 F pulseaudio BuildID: 20201006011220 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 18:55:14 2020 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-10-04 (31 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.45 metric 100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.0/20200629202523 (Out of date) Profile0 (Default) - LastVersion=78.3.2/20201006011220 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.release: 4.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AGH6120H.86A.0015.2012.0926.1822 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61AGL dmi.board.vendor: Intel Corporation dmi.board.version: G71256-202 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: sabc1 dmi.modalias: dmi:bvnIntelCorp.:bvrAGH6120H.86A.0015.2012.0926.1822:bd09/26/2012:br4.6:svnSystem76,Inc.:pnSableComplete:pvrsabc1:rvnIntelCorporation:rnDH61AGL:rvrG71256-202:cvnSystem76,Inc.:ct3:cvrsabc1: dmi.product.family: To be filled by O.E.M. dmi.product.name: Sable Complete dmi.product.sku: To be filled by O.E.M. dmi.product.version: sabc1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902969/+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 1902918] Re: GDM crashes after upgrade to 20.10 due to apparmor and snap
*** This bug is a duplicate of bug 1898005 *** https://bugs.launchpad.net/bugs/1898005 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1898005, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1898005 gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() -- 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/1902918 Title: GDM crashes after upgrade to 20.10 due to apparmor and snap Status in gnome-shell package in Ubuntu: Incomplete Bug description: Releases: - Ubuntu 20.10 running Wayland - apparmor 3.0.0-0ubuntu1 Error description: After upgrading from Ubuntu 20.04 to 20.10 my GDM crashes regularly even without user interaction when the computer is left unused. After the crash the purple login screen shows and all open programs have been terminated (and unsaved data is lost). dmesg reveals that the issue is related to the "Ubuntu Software" Snap application in conjunction with apparmor. Probably the issue occurs when Ubuntu Software app is checking for updates in the background - hence it occurs without user interaction. Further information: The issue has also been described by other users: - https://askubuntu.com/questions/1230654/ubuntu-20-04-rebooting-and-freezing - https://www.dell.com/community/XPS/Ubuntu-20-04-XPS-13-crashes-and-logs-me-out/td-p/7623758 I attached the dmesg output Best regards, Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902918/+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 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()
** Description changed: + See also bug 1898910 + + --- + Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=en_CA.UTF-8 - LANGUAGE=en_CA:en - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_CA.UTF-8 + LANGUAGE=en_CA:en + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: - () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /usr/lib/gnome-shell/libst-1.0.so - g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 - () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/gnome-shell/libst-1.0.so + g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: See also bug 1898910 --- Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT 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/1898005/+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 1902853] Re: Failure to create core GL context with llvmpipe when using GLX_ARB_context_flush_control
OK, thanks. In that case the correct status of the bug is "Fix Released". If we knew *what* change fixed it then we could try to get the same fix into 18.04. Probably Mesa, I guess? ** Changed in: libsdl2 (Ubuntu) Status: Incomplete => Fix Released ** Changed in: mesa (Ubuntu) Status: Incomplete => 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/1902853 Title: Failure to create core GL context with llvmpipe when using GLX_ARB_context_flush_control Status in libsdl2 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: When using llvmpipe on the non-HWE xorg version GL core context creation fails when using "GLX_ARB_context_flush_control" even though the driver reports that the extension is supported. Apologies if xorg is the wrong package here, this could be a libgl1 -mesa-dri/glx bug instead, it's unclear to me where the fault lies in the graphics stack. xserver-common: Installed: 2:1.19.6-1ubuntu4.7 Candidate: 2:1.19.6-1ubuntu4.7 linux-generic: Installed: 4.15.0.122.109 Candidate: 4.15.0.122.109 Steps to reproduce on Ubuntu Server: 1. Install Ubuntu 18.04 server edition in a VM, or other hardware without a physical graphics device 2. Install the desktop with "sudo apt install ubuntu-desktop" 3. Reboot 4. Compile and run the attached file Steps to reproduce on Ubuntu Desktop: 1. Install Ubuntu 18.04 desktop edition in a VM, or other hardware without a physical graphics device 2. Remove the HWE packages with "apt remove *-hwe-18.04" and then "apt install xserver-xorg-core ubuntu-desktop xserver-xorg xserver-xorg-video-all xserver-xorg-input-all libgl1-mesa-dri libgl1-mesa-glx" to get things back to normal 3. Reboot 4. Compile and run the attached file Both examples produce: "Could not create GL context: BadValue (integer parameter out of range for operation)" For both cases, upgrading to (or staying on) the HWE stack allows creating the core 3.3 context successfully. Debugging: I've stepped all the way into libxcb for the context creation at src/glx.c:3258, with a call to "xcb_glx_create_context_attribs_arb_checked", but haven't managed to link this up to a received request in another process. The request is rejected with BadValue. BadVaue in this instance could mean one of two things according to GL spec: 1. The GLX_RENDER_TYPE attribute is invalid 2. An attribute or it's bitmask are not recognized. We can likely rule out 1 as GLX_RENDER_TYPE is correctly set to opengl. Option 2 allows looking at it at a higher level. SDL2 adds `GLX_CONTEXT_RELEASE_BEHAVIOUR_ARB=GLX_CONTEXT_RELEASE_BEHAVIOUR_FLUSH_ARB` to the attributes (at src/video/x11/SDL_x11opengl.c:720) by default when it detects the `GLX_ARB_context_flush_control` extension is present, which should be a no-op and the default setting. `glxinfo` and other gl functions all show that `GLX_ARB_context_flush_control` is present, but removing that usage from the attributes list (by removing lines 720 to 726 avoids the issue and we are given a valid GL context. Due to this, I think something in the graphics stack is rejecting the usage of GLX_ARB_context_flush_control, even though it's claiming to support it through other gl calls. The llvmpipe GL driver reports core support up to 3.3 as well, so this shouldn't be an issue. I also suspect it's simply something that's been fixed more recently, as installing the newer HWE versions of xorg (and the kernel) fixes the issue. I wouldn't expect to have to upgrade to the HWE stack to be able to get a working GL context this way, so I'm reporting this to check if it's a known issue or if there's a fix that can be made. The attached file depends on "libsdl2-dev" and can be compiled and run with: "g++ main.cpp -I/usr/include/SDL2 -lSDL2 -lGL && ./a.out" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 09:16:16 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-11-03 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEn
[Desktop-packages] [Bug 1902918] Re: GDM crashes after upgrade to 20.10 due to apparmor and snap
*** This bug is a duplicate of bug 1898005 *** https://bugs.launchpad.net/bugs/1898005 I should have guessed this was gnome-shell, since that provides the GUI, not GDM... Nov 05 17:39:44 daniel-ThinkPad-X1 gnome-shell[5778]: ** Nov 05 17:39:44 daniel-ThinkPad-X1 gnome-shell[5778]: St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL) Nov 05 17:39:44 daniel-ThinkPad-X1 gnome-shell[5778]: Bail out! St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL) Nov 05 17:39:44 daniel-ThinkPad-X1 gnome-shell[5778]: GNOME Shell crashed with signal 6 Nov 05 17:39:44 daniel-ThinkPad-X1 gnome-shell[5778]: == Stack trace for context 0x556da2fb7130 == Nov 05 17:39:44 daniel-ThinkPad-X1 gnome-shell[5778]: #0 556da6f4e6e0 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:234 (c4c26ca09c0 @ 10) Nov 05 17:39:44 daniel-ThinkPad-X1 gnome-shell[5778]: #1 7ffc36404e40 b self-hosted:225 (25141f3a58d0 @ 273) Nov 05 17:39:44 daniel-ThinkPad-X1 gnome-shell[5778]: #2 556da6f4e648 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:234 (c4c26ca0a10 @ 43) Nov 05 17:39:44 daniel-ThinkPad-X1 gnome-shell[5778]: #3 556da6f4e5b8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:209 (c4c26ca0b50 @ 32) Nov 05 17:39:44 daniel-ThinkPad-X1 gnome-shell[5778]: #4 556da6f4e4b8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:460 (c4c26ca0330 @ 650) Nov 05 17:39:44 daniel-ThinkPad-X1 gnome-shell[5778]: #5 556da6f4e418 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:340 (c4c26ca0650 @ 21) -- 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/1902918 Title: GDM crashes after upgrade to 20.10 due to apparmor and snap Status in gnome-shell package in Ubuntu: Incomplete Bug description: Releases: - Ubuntu 20.10 running Wayland - apparmor 3.0.0-0ubuntu1 Error description: After upgrading from Ubuntu 20.04 to 20.10 my GDM crashes regularly even without user interaction when the computer is left unused. After the crash the purple login screen shows and all open programs have been terminated (and unsaved data is lost). dmesg reveals that the issue is related to the "Ubuntu Software" Snap application in conjunction with apparmor. Probably the issue occurs when Ubuntu Software app is checking for updates in the background - hence it occurs without user interaction. Further information: The issue has also been described by other users: - https://askubuntu.com/questions/1230654/ubuntu-20-04-rebooting-and-freezing - https://www.dell.com/community/XPS/Ubuntu-20-04-XPS-13-crashes-and-logs-me-out/td-p/7623758 I attached the dmesg output Best regards, Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902918/+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 1903230] Re: Mutter release 3.36.7
"Fix Released" just because we already released 3.38 but I will also nominate focal to get 3.36.7 released properly. ** Tags added: rls-ff-incoming -- 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/1903230 Title: Mutter release 3.36.7 Status in mutter package in Ubuntu: Fix Released Bug description: We should release mutter 3.36.7 to focal, for bug 1900906, bug 1894596 and ...? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+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 1902749] Re: [amdgpu] Log in screen flashes on and off until I log in
Please try to find an older kernel version that does boot, to see if there were any that didn't have the bug... https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1902749 Title: [amdgpu] Log in screen flashes on and off until I log in Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Im on Ubuntu 20.04.1 with an AMD Ryzen 7 4800h CPU and a Nvidia GTX 1650ti [Mobile] GPU using nvidia-driver-450 Kernel is up to date (5.9.3) When my laptop boots, the log in screen flashes black and quickly back on until i log in. When i reach the desktop the flashing stops. Still, having the screen flickering on the log in screen is very annoying. As far as i can tell, the laptop doesn't have any further screen issues. Thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.9.3-050903-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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) 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 17:46:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU116M [GeForce GTX 1650 Ti Mobile] [10de:2192] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited Device [1d05:1101] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited Renoir [1d05:1100] InstallationDate: Installed on 2020-10-27 (7 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Standard GK5NPFO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.3-050903-generic root=UUID=a7144690-52e4-4688-a61a-b208b0648077 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.16PCS01 dmi.board.asset.tag: Standard dmi.board.name: GK5NPFO dmi.board.vendor: TongFang dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: Standard dmi.chassis.version: Standard dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.16PCS01:bd09/01/2020:br5.16:efr1.22:svnStandard:pnGK5NPFO:pvrStandard:rvnTongFang:rnGK5NPFO:rvrStandard:cvnStandard:ct10:cvrStandard: dmi.product.family: Standard dmi.product.name: GK5NPFO dmi.product.sku: 0001 dmi.product.version: Standard dmi.sys.vendor: Standard version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/linux/+bug/1902749/+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 1903230] [NEW] Mutter release 3.36.7
Public bug reported: We should release mutter 3.36.7 to focal, for bug 1900906, bug 1894596 and ...? ** Affects: mutter (Ubuntu) Importance: Medium Status: Fix Released ** Tags: focal rls-ff-incoming ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => Triaged ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released -- 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/1903230 Title: Mutter release 3.36.7 Status in mutter package in Ubuntu: Fix Released Bug description: We should release mutter 3.36.7 to focal, for bug 1900906, bug 1894596 and ...? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+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 1901413] Re: Sound Blaster Audigy 5/Rx cannot be configured as input/output
** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released ** Tags added: fixed-in-13.99.2 fixed-upstream -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+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 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell
Yes, done in bug 1903230 -- 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/1900906 Title: Can't use dead keys or input e.g. Chinese characters in GNOME shell Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. Under X, if I try to input an accentuated character, such as á or ü, in places like the search field in the overview or when writing a folder name in the app grid, nothing appears. Under Wayland, it fails each time on the first input of an accentuated character, then it works. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-01 (174 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Package: ibus PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago) UserGroups: sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1900906/+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 1902825] Re: High CPU usage just moving the mouse
I mean; does 'top' report constant CPU without moving the mouse, or was that only with gnome-system-monitor? (bug 1773502) -- 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/1902825 Title: High CPU usage just moving the mouse Status in gnome-shell package in Ubuntu: Incomplete Bug description: high cpu usage just moving the mouse removed appindicator extension .. the cpu load is very high. running strace -c -p while moving mouse % time seconds usecs/call callserrors syscall -- --- --- - - 36.740.103852 103 1000 8 futex 31.300.088469 8 10366 8750 recvmsg 15.530.043901 11 3925 poll 10.100.028550 10 2776 write 4.330.012232 7 1537 writev 1.600.004533 4 932 read 0.390.001092 3 337 getpid 0.000.01 0 2 getrusage 0.000.01 1 1 restart_syscall 0.000.00 0 4 mprotect -- --- --- - - 100.000.282631 20880 8758 total ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Nov 4 10:49:20 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902825/+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 1893300] Re: The status of cups still shows idle when the printer has been unplugged
@Łukasz, updated, please help to review again, thanks. ** Description changed: [ Impact ] After printers (non-ippusb protocal) have been disconnected, the status of cups still shows "idle" instead of "disabled", so seems the disconnected procedure hasn't worked well. [ Test Case ] 1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 20.04 machine 2. Wait for the status of cups became "Idle" (lpstat -p) 3. Unplug the cable of the printer 4. Check the status of cups again. (lpstat -p) [ Regression potential ] - Low, the change just makes "strcmp" to "srtsrt" and has more checks on the existing of device path. + Very Low, if something went wrong in the change, then this issue happened again, due to this snippet will only be called during printer removed event. [Expected result] The status should show disabled. [Actual result] The status shows idle. [info] Target: HP LaserJet Pro203dw HP Officejet 100 Mobile Printer HP Officeject 200 Mobile Printer Brother HL-2250DN Samsung ML-331x Upstream Bug: https://github.com/OpenPrinting/system-config- printer/issues/182 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged Status in OEM Priority Project: Triaged Status in OEM Priority Project focal series: New Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Focal: Incomplete Status in system-config-printer source package in Groovy: Incomplete Bug description: [ Impact ] After printers (non-ippusb protocal) have been disconnected, the status of cups still shows "idle" instead of "disabled", so seems the disconnected procedure hasn't worked well. [ Test Case ] 1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 20.04 machine 2. Wait for the status of cups became "Idle" (lpstat -p) 3. Unplug the cable of the printer 4. Check the status of cups again. (lpstat -p) [ Regression potential ] Very Low, if something went wrong in the change, then this issue happened again, due to this snippet will only be called during printer removed event. [Expected result] The status should show disabled. [Actual result] The status shows idle. [info] Target: HP LaserJet Pro203dw HP Officejet 100 Mobile Printer HP Officeject 200 Mobile Printer Brother HL-2250DN Samsung ML-331x Upstream Bug: https://github.com/OpenPrinting/system-config- printer/issues/182 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
This is getting too complicated to handle as an SRU considering that it's a not-so-important issue after all. So I think we should simply revert the problematic gnome-terminal commit in groovy only, and hope that upstream sorts it out for hirsute. So I would like to upload this fix to groovy: https://launchpad.net/~gunnarhj/+archive/ubuntu/gnome-terminal But I can't do that until the version in hirsute is bumped somehow... ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Also affects: pango1.0 (Ubuntu) Importance: Undecided Status: New ** No longer affects: pango1.0 (Ubuntu Groovy) ** Changed in: gtk+3.0 (Ubuntu Groovy) Status: Fix Committed => Won't Fix ** Changed in: gtk+3.0 (Ubuntu Groovy) Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned) ** Changed in: gnome-terminal (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: gnome-terminal (Ubuntu Groovy) Status: New => Triaged ** Changed in: gnome-terminal (Ubuntu Groovy) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gnome-terminal package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Fix Committed Status in pango1.0 package in Ubuntu: New Status in gnome-terminal source package in Groovy: Triaged Status in gtk+3.0 source package in Groovy: Won't Fix Bug description: [Impact] When you want to select a monospace font in gnome-terminal's profile editor, it does not always show the regular font but rather an arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an upstream commit which fixes it. [Test case] * Install the binaries built from gtk+3.0 in groovy-proposed * Relogin * Open gnome-terminal -> Preferences and open the window for selecting a custom font for the profile. Find that it shows regular fonts only. [ Regression risk ] The upstream commit was written explicitly to fix this issue, so the regression risk should be low. Please note that the only affected file is gtk/gtkfontchooserwidget.c, so the scope is very limited which in itself ought to limit the regression risk. [Original description] trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+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 1903224] Re: Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used
** Package changed: ubuntu => metacity (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1903224 Title: Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used Status in metacity package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Package: Xorg or Gnome, not really sure. Problem description: 1. I have set the Launch terminal shortcut in Settings/Keyboard shortcuts to CTRL+`. 2. I invoke the activities overview by pressing SUPER once. 3. I launch a terminal by pressing the newly set CTRL+` shortcut. What happened: two new terminal windows appeared. What is expected: launch only one terminal window. More info: This only happens when a CTRL modifier is used and the key is set to a non function (F1-F12) key. When an ALT or CTRL+ALT shortcut is used, only one window appears, as expected. Expected behaviour: launch only one terminal window while in the activities overview. What happened: two new terminal windows appeared in the activities overview. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1903224/+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 1903224] [NEW] Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used
You have been subscribed to a public bug: lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 Package: Xorg or Gnome, not really sure. Problem description: 1. I have set the Launch terminal shortcut in Settings/Keyboard shortcuts to CTRL+`. 2. I invoke the activities overview by pressing SUPER once. 3. I launch a terminal by pressing the newly set CTRL+` shortcut. What happened: two new terminal windows appeared. What is expected: launch only one terminal window. More info: This only happens when a CTRL modifier is used and the key is set to a non function (F1-F12) key. When an ALT or CTRL+ALT shortcut is used, only one window appears, as expected. Expected behaviour: launch only one terminal window while in the activities overview. What happened: two new terminal windows appeared in the activities overview. ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used https://bugs.launchpad.net/bugs/1903224 You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903176] Re: Ubuntu crashes many times and go to login screen while browosing site in firefox version -82
Thank you for taking the time to report this bug and helping to make Ubuntu better. If GNOME-shell suffers from a crash, all programs are killed & the user is logged out. There can be many reasons for this, however it's not related to the `ubuntu-release-upgrader` package which upgrades a release (from focal/20.04 to groovy/20.10 for example) I'm not sure what package this should be filed against, I see only evidence of i915/graphic crash, but little detail is available (partially as filed against the upgrade tool). ** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1903176 Title: Ubuntu crashes many times and go to login screen while browosing site in firefox version -82 Status in ubuntu-meta package in Ubuntu: New Bug description: I have upgraded from Ubuntu 20.04 to 20.10 recently and I have noticed that while browsing sites in Firefox especially using Youtube in Firefox, the System crashes and go to Login screen. all the application used are closed and need to reopen again. I am using 4 GB RAM 64 Bit Ubuntu. Kindly fix. Thank You so much - Arise ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.12 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Nov 5 23:52:18 2020 InstallationDate: Installed on 2017-10-04 (1127 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-24 (11 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1903176/+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 1903176] [NEW] Ubuntu crashes many times and go to login screen while browosing site in firefox version -82
You have been subscribed to a public bug: I have upgraded from Ubuntu 20.04 to 20.10 recently and I have noticed that while browsing sites in Firefox especially using Youtube in Firefox, the System crashes and go to Login screen. all the application used are closed and need to reopen again. I am using 4 GB RAM 64 Bit Ubuntu. Kindly fix. Thank You so much - Arise ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.12 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Nov 5 23:52:18 2020 InstallationDate: Installed on 2017-10-04 (1127 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-24 (11 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy -- Ubuntu crashes many times and go to login screen while browosing site in firefox version -82 https://bugs.launchpad.net/bugs/1903176 You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902969] Re: desktop freezes when changing thundebird win decorations
How do I add that w/o having to submit a new bug? -- 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/1902969 Title: desktop freezes when changing thundebird win decorations Status in gnome-shell package in Ubuntu: New Bug description: I noticed a bug. In Thunderbird (deb or snap) version open and right click on the tab bar and choose customization and mess around with showing title or not and close out of it the icon for TB is still in the dock. If you click on the icon it locks up the UI. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.3.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mram 2160 F pulseaudio /dev/snd/controlC0: mram 2160 F pulseaudio BuildID: 20201006011220 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 18:55:14 2020 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-10-04 (31 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.45 metric 100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.0/20200629202523 (Out of date) Profile0 (Default) - LastVersion=78.3.2/20201006011220 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.release: 4.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AGH6120H.86A.0015.2012.0926.1822 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61AGL dmi.board.vendor: Intel Corporation dmi.board.version: G71256-202 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: sabc1 dmi.modalias: dmi:bvnIntelCorp.:bvrAGH6120H.86A.0015.2012.0926.1822:bd09/26/2012:br4.6:svnSystem76,Inc.:pnSableComplete:pvrsabc1:rvnIntelCorporation:rnDH61AGL:rvrG71256-202:cvnSystem76,Inc.:ct3:cvrsabc1: dmi.product.family: To be filled by O.E.M. dmi.product.name: Sable Complete dmi.product.sku: To be filled by O.E.M. dmi.product.version: sabc1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902969/+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 1890365] Re: [snap] Web Serial fails to access local device
'''
$ snap connections chromium | grep usb
raw-usb chromium:raw-usb :raw-usb manual
$ journalctl -f | grep chromium
Nov 05 18:41:42 XX audit[80101]: AVC apparmor="DENIED" operation="open"
profile="snap.chromium.chromium" name="/proc/tty/drivers" pid=80101
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
... repeated several times
Nov 05 18:42:05 XX polkitd(authority=local)[1133]: Operator of
unix-session:c2 successfully authenticated as unix-user:X to gain TEMPORARY
authorization for action io.snapcraft.snapd.manage-interfaces for
unix-process:80462:133089573 [snap connect chromium:raw-usb] (owned by
unix-user:X)
'''
The alert dialog reports "No compatible devices found"
--
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/1890365
Title:
[snap] Web Serial fails to access local device
Status in chromium-browser package in Ubuntu:
New
Bug description:
A javascript-based web page works fine when accessed through Chrome,
fails to recognize that any devices exist when accessed from Chromium
on the same Unubtu 20.04 platform.
The code includes the following snippet:
const requestOptions = {
filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();
Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
is listed in the pop-up, is selectable, and can communicate. Under
Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
contains only "No compatible devices found" message.
Experimental Web Features flag is enabled in both browsers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+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
@Hui Wang, no is not a package, the Make generated *.so or something like that -- 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 240133] Re: MHTML Format - Web Archive Files - Standard not supported in Firefox
** Changed in: firefox Importance: Wishlist => Medium -- 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+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 240133]
*** Bug 1336793 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+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 240133]
(In reply to ajf from comment #101)
> It's a shame that after 18 years, Mozilla still has no support for MIME
> HTML. If I knew C++ and the codebase, I'd write a patch, but alas.
There is actually an alternative solution and we don't need to know C++.
It was suggested in comment #78 and confirmed in comment #93: use the
add-on called UnMHT (https://addons.mozilla.org/en-
US/firefox/addon/unmht/) I also can confirm it's working good. I'm
pretty sure it can be integrated inside Firefox setup so that it's
enabled by default. Look, Calendar project used to be an add-on for
Thunderbird. Now in TB 38, the add-on is integrated and works
perfectly. So why not UnMHT?
I've seen comment #95 saying that it does not work for him. Maybe the
commentator didn't use the right method? We cannot put the xpi file like that
inside "extension" folder. In all cases, the file name has to be changed. In
some cases, it's also necessary to unpack the file. For UnMHT, filename change
is enough. Here are the steps for FF 40:
1. Download unmht-8.0.0-an+sm+tb+fx.xpi from
https://addons.mozilla.org/en-US/firefox/addon/unmht/
2. Change the name to {f759ca51-3a91-4dd1-ae78-9db5eee9ebf0}.xpi
3. Put it into "extension" folder. There are two extension folders in Windows:
a. System-wide:
Put it in "C:\Program Files (x86)\Mozilla Firefox\browser\extensions" and
whoever logs in the computer will get the add-on.
b. User-wide:
Put it in
C:\Users\\AppData\Roaming\Mozilla\Firefox\Profiles\\extensions
so that only will get it
4. In either case, it's still necessary to explicitly enable the add-on.
--
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/240133
Title:
MHTML Format - Web Archive Files - Standard not supported in Firefox
Status in Mozilla Firefox:
Won't Fix
Status in firefox package in Ubuntu:
Triaged
Bug description:
Binary package hint: firefox-3.0
this location http://www.militarybadges.org.uk/badget11.mht
displays
This document is a Web archive file. If you are seeing this message, this
means your browser or editor doesn't support Web archive files. For more
information on the Web archive format, go to
http://officeupdate.microsoft.com/office/webarchive.htm
I am using ubuntu 8.04
ProblemType: Bug
Architecture: i386
Date: Sun Jun 15 10:28:40 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: nvidia
Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1
PackageArchitecture: i386
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-18-generic i686
WORKAROUND :
http://www.unmht.org/unmht/en_index.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/240133/+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 240133]
But marking it as WONTFIX means that there's been a conscious decision made not to implement it, right? Here it's just a case that nobody's done it. It might be done someday. -- 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+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 240133]
RFC 2557 MHTML is a standarized format for web page archive that deemed to be directly readable for web browsers and is already supported by many browsers such as IE and Chrome. However, Firefox does not directly support it. Although we currently have addons like MAF (https://addons.mozilla.org/zh-tw/firefox/addon /mozilla-archive-format/) or UnMHT (https://addons.mozilla.org/zh- tw/firefox/addon/unmht/), they are written in XUL/XPCOM, which is going to be deprecated, and their functionality is currently not available in WebExtension, the exclusively addon system in the future. Therefore, we need a support for RFC 2557 MHTML support, at least a directly reading, and saving at best. This could either be: 1. Directly support for MHTML reading and writing 2. Add enough API to allow an addon like MAF or UnMHT in WebExtension -- 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+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 240133]
Now that UmMHT etc. do not work anymore the only add-on supporting mht is Save Page WE, but it only has support for saving pages as mht, not for opening them. -- 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+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 240133]
(In reply to 石庭豐 (Seak, Teng-Fong) from comment #102) Teng-Fong, I believe you're mistaken. The core issue with MIME support is that it's based on code which is essentially a custom object system implemented in C, with polymorphic construction by class name, and other strangeness. It is very tricky to work with, and what's _really_ necessary is getting rid of it in favor of a proper C++'ish MIME library. Problem is, it's like a house of cards which collapses on top of you when you do that. Last decade I had tried to initiate this kind of a rewrite, but it didn't work out. See also Arho's comment #95. Anyway, something like UnMHT are not really a solution, it's a workaround; and it would not be reasonable to integrate it. It would be yet another layer over the problematic core. -- 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+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 240133]
(In reply to 石庭豐 (Seak, Teng-Fong) from comment #102) Teng-Fong, I believe you're mistaken. The core issue with MIME support is that it's based on code which is essentially a custom object system implemented in C, with polymorphic construction by class name, and other strangeness. It is very tricky to work with, and what's _really_ necessary is getting rid of it in favor of a proper C++'ish MIME library. Problem is, it's like a house of cards which collapses on top of you when you do that. Last decade I had tried to initiate this kind of a rewrite, but it didn't work out. See also Arho's comment #95. Anyway, something like UnMHT are not really a solution, it's a workaround; and it would not be reasonable to integrate it. It would be yet another layer over the problematic core. -- 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+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 240133]
This isn't on anyone's roadmap and nobody has provided a patch for it in 15 years - so its just clogging up bugzilla. That doesn't mean it isn't a good idea - it just means nobody is planning on working on it. If someone works on it then this should be opened as a new issue. -- 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+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 240133]
Patrick, could you please provide a link to the source of, or just state/quote the reasoning behind, the decision to resolve this as WONTFIX? -- 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+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 240133]
It's a shame that after 18 years, Mozilla still has no support for MIME HTML. If I knew C++ and the codebase, I'd write a patch, but alas. I hope this comment might remind someone this exists and spur them into action. -- 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+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 240133]
How will someone looking for things to work on find this request? -- 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+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 1903207] Re: Fast forwards through files without playing when Crossfade Playback is enabled ( in gstreamer 1.18+ )
Fixed in upstream commit: https://gitlab.gnome.org/GNOME/rhythmbox/-/commit/3360f18d15cd6fabcadac56bc07d4ca133fa661f -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1903207 Title: Fast forwards through files without playing when Crossfade Playback is enabled ( in gstreamer 1.18+ ) Status in rhythmbox package in Ubuntu: New Bug description: Playback fails when crossfade is enabled in gstreamer 1.18+ Upstream bug: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1835 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1903207/+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 1903207] [NEW] Fast forwards through files without playing when Crossfade Playback is enabled ( in gstreamer 1.18+ )
Public bug reported: Playback fails when crossfade is enabled in gstreamer 1.18+ Upstream bug: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1835 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1903207 Title: Fast forwards through files without playing when Crossfade Playback is enabled ( in gstreamer 1.18+ ) Status in rhythmbox package in Ubuntu: New Bug description: Playback fails when crossfade is enabled in gstreamer 1.18+ Upstream bug: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1835 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1903207/+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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
I also have the same problem now on Pop!_OS 20.04 after installing some updates. I suspect libasound2:amd64 (1.2.2-2.1ubuntu2, 1.2.2-2.1ubuntu2.1) beeing responsible, since this is the only sound related update that I installed today. I also tried 20.10 two weeks ago and had the exact same issue there, so I went back to 20.04 ... -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE 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.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1903200] Re: Ubuntu is unable to detect one of my GPUs
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1903200 Title: Ubuntu is unable to detect one of my GPUs Status in xorg package in Ubuntu: New Bug description: I have an MSI laptop which was working fine with Ubuntu 18, but I decided to upgrade. It has one of these dual graphics setups, which and Intel HD 630 and a NVIDIA GTX 1060 6GB. On Ubuntu 18, I simply get the NVIDIA GPU to work by selecting its drivers on the "Additional Drivers" tab under "Software and Updates", but on this version of Ubuntu, my GPU doesn't appear there any more. Also, if I type this in the console: $ lspci | grep -i --color 'vga\|3d\|2d' This is the only line I get: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) Just in case, my laptop model is this: https://es.msi.com/Laptop /GL72VR-7RFX I also have Windows on dual boot and the GPU works perfectly fine there. Also, it is not disabled on the BIOS or something like that. I don't think that is even possible on my BIOS either. $ lspci -k | grep -EA3 'VGA|3D|Display' 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) DeviceName: Onboard IGD Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 630 Kernel driver in use: i915 $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA Controller [AHCI Mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) 00:1c.3 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #4 (rev f1) 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1f.0 ISA bridge: Intel Corporation HM175 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 02:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) 03:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10) 04:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller Looking at the output, I don't know why it says that my processor is an Intel Xeon... it's actually a i7-7700HQ. Here is a thread on the forum with more people experiencing this issue: https://ubuntuforums.org/showthread.php?t=2443007 Any help would be appreciated. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 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.10 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 5 20:18:37 2020 DistUpgraded: 2020-05-08 15:27:01,107 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-51-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 630 [1462:11d7] InstallationDate: Installed on 2018-10-02 (765 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Micro-Star International Co., Lt
[Desktop-packages] [Bug 1903200] [NEW] Ubuntu is unable to detect one of my GPUs
You have been subscribed to a public bug: I have an MSI laptop which was working fine with Ubuntu 18, but I decided to upgrade. It has one of these dual graphics setups, which and Intel HD 630 and a NVIDIA GTX 1060 6GB. On Ubuntu 18, I simply get the NVIDIA GPU to work by selecting its drivers on the "Additional Drivers" tab under "Software and Updates", but on this version of Ubuntu, my GPU doesn't appear there any more. Also, if I type this in the console: $ lspci | grep -i --color 'vga\|3d\|2d' This is the only line I get: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) Just in case, my laptop model is this: https://es.msi.com/Laptop/GL72VR- 7RFX I also have Windows on dual boot and the GPU works perfectly fine there. Also, it is not disabled on the BIOS or something like that. I don't think that is even possible on my BIOS either. $ lspci -k | grep -EA3 'VGA|3D|Display' 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) DeviceName: Onboard IGD Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 630 Kernel driver in use: i915 $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA Controller [AHCI Mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) 00:1c.3 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #4 (rev f1) 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1f.0 ISA bridge: Intel Corporation HM175 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 02:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) 03:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10) 04:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller Looking at the output, I don't know why it says that my processor is an Intel Xeon... it's actually a i7-7700HQ. Here is a thread on the forum with more people experiencing this issue: https://ubuntuforums.org/showthread.php?t=2443007 Any help would be appreciated. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 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.10 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 5 20:18:37 2020 DistUpgraded: 2020-05-08 15:27:01,107 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-51-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 630 [1462:11d7] InstallationDate: Installed on 2018-10-02 (765 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Micro-Star International Co., Ltd. GL72VR 7RFX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=97a38a40-3df8-4990-a5bf-b879b481309b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-08 (181 days ago) XorgLogOld: dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends I
[Desktop-packages] [Bug 1891270] Re: Iranian calendar shows in Azerbaijani language
This bug also persisted in Ubuntu 20.10 with ubiquity 20.10.13 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1891270 Title: Iranian calendar shows in Azerbaijani language Status in gnome-calendar package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: I already installed Ubuntu 20.04.1 LTS and set location on Iran during installation. After finishing installation successfully, I open the calendar by clicking at the top of the screen (where the clock is shown), I see the calendar with Azerbaijani names for month and weekdays. Such as "آقوست" for August and "جومعه آخشامی" for Thursday. But it should show in Iranian names such as "اوت" for August and "پنجشنبه" for Thursday. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup
I can confirm that the issue still persists with pulseaudio 13.99.3 from the ppa. Will report details upstream. -- 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/1901922 Title: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW 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.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1901922/+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 1903197] [NEW] Update to 82.0.2
Public bug reported: See https://www.mozilla.org/en-US/firefox/82.0.2/releasenotes/ ** Affects: firefox (Ubuntu) Importance: Undecided Status: Fix Released ** Changed in: firefox (Ubuntu) Status: New => 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/1903197 Title: Update to 82.0.2 Status in firefox package in Ubuntu: Fix Released Bug description: See https://www.mozilla.org/en-US/firefox/82.0.2/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1903197/+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 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
I'm facing a similar problem. May I ask your alsa-utils version? Is it 1.2.2-1ubuntu2 or 1.2.2-1ubuntu1? My issues started when the system updated to alsa-utils 1.2.2-1ubuntu2. -- 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/1901926 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 13:48:59 2020 InstallationDate: Installed on 2020-01-14 (287 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) dmi.bios.date: 11/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03REZ.041.191104.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P03REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+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 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1901926 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 13:48:59 2020 InstallationDate: Installed on 2020-01-14 (287 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) dmi.bios.date: 11/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03REZ.041.191104.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P03REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+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 1082110]
A compatibility option was added for DOC format here that could be adapted to DOCX/RTF too: https://bugs.documentfoundation.org/show_bug.cgi?id=124601#c8 -- 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/1082110 Title: [Upstream] Endnote placed at end of document is unmovable Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.6.2~rc2-0ubuntu4 Candidate: 1:3.6.2~rc2-0ubuntu4 Version table: *** 1:3.6.2~rc2-0ubuntu4 0 900 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.6.2~rc2-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 3) What is expected to happen in Calc is open a blank document -> type example -> click Insert -> Footnote/Endnote... -> under Numbering click radio button Automatic -> under Type click radio button Endnote -> click button OK and an Endnote is inserted one line down from example, which one may click Enter on the keyboard, moving the Endnote one line down, as it does in Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit). 4) What happens instead is the Endnote is placed all the way at the bottom of the document, and is not movable via clicking Del on the keyboard. WORKAROUND: Use AbiWord. apt-cache policy abiword abiword: Installed: 2.9.2+svn20120603-8 Candidate: 2.9.2+svn20120603-8 Version table: *** 2.9.2+svn20120603-8 0 500 http://archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages 100 /var/lib/dpkg/status Open a blank document -> type example -> click References -> Insert Endnote and an Endnote is inserted one line down from example, which one may click Enter on the keyboard, moving the Endnote one line down. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-writer 1:3.5.4-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 Date: Thu Nov 22 09:03:21 2012 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1082110/+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 1082110] Re: [Upstream] Endnote placed at end of document is unmovable
** Bug watch added: Document Foundation Bugzilla #124601 https://bugs.documentfoundation.org/show_bug.cgi?id=124601 -- 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/1082110 Title: [Upstream] Endnote placed at end of document is unmovable Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.6.2~rc2-0ubuntu4 Candidate: 1:3.6.2~rc2-0ubuntu4 Version table: *** 1:3.6.2~rc2-0ubuntu4 0 900 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.6.2~rc2-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 3) What is expected to happen in Calc is open a blank document -> type example -> click Insert -> Footnote/Endnote... -> under Numbering click radio button Automatic -> under Type click radio button Endnote -> click button OK and an Endnote is inserted one line down from example, which one may click Enter on the keyboard, moving the Endnote one line down, as it does in Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit). 4) What happens instead is the Endnote is placed all the way at the bottom of the document, and is not movable via clicking Del on the keyboard. WORKAROUND: Use AbiWord. apt-cache policy abiword abiword: Installed: 2.9.2+svn20120603-8 Candidate: 2.9.2+svn20120603-8 Version table: *** 2.9.2+svn20120603-8 0 500 http://archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages 100 /var/lib/dpkg/status Open a blank document -> type example -> click References -> Insert Endnote and an Endnote is inserted one line down from example, which one may click Enter on the keyboard, moving the Endnote one line down. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-writer 1:3.5.4-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 Date: Thu Nov 22 09:03:21 2012 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1082110/+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 1902832] Re: lftp support broken - exits with error_code -11 on Bionic
Simpler reproducer: valgrind lftp -e 'get gnu/glibc/nss_db-2.2.tar.gz;exit' ftp.gnu.org ==9023== Memcheck, a memory error detector ==9023== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==9023== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==9023== Command: lftp -e get\ gnu/glibc/nss_db-2.2.tar.gz;exit ftp.gnu.org ==9023== ==9024== .gnu.org' [Resolving host address...] ==9024== HEAP SUMMARY: ==9024== in use at exit: 209,311 bytes in 1,703 blocks ==9024== total heap usage: 4,136 allocs, 2,433 frees, 579,083 bytes allocated ==9024== ==9024== LEAK SUMMARY: ==9024==definitely lost: 0 bytes in 0 blocks ==9024==indirectly lost: 0 bytes in 0 blocks ==9024== possibly lost: 3,109 bytes in 41 blocks ==9024==still reachable: 206,202 bytes in 1,662 blocks ==9024== suppressed: 0 bytes in 0 blocks ==9024== Rerun with --leak-check=full to see details of leaked memory ==9024== ==9024== For counts of detected and suppressed errors, rerun with: -v ==9024== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) get: gnu/glibc/nss_db-2.2.tar.gz: /home/ubuntu/nss_db-2.2.tar.gz: file already exists and xfer:clobber is unset ==9023== Invalid read of size 4 ==9023==at 0x2184B0: AddXfer (RateLimit.cc:30) ==9023==by 0x2184B0: RateLimit::~RateLimit() (RateLimit.cc:63) ==9023==by 0x218B18: dispose (xmap.h:107) ==9023==by 0x218B18: xmap_p::~xmap_p() (xmap.h:112) ==9023==by 0x6224160: __run_exit_handlers (exit.c:108) ==9023==by 0x6224259: exit (exit.c:139) ==9023==by 0x6202BFD: (below main) (libc-start.c:344) ==9023== Address 0x8072550 is 16 bytes inside a block of size 88 free'd ==9023==at 0x4C3323B: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==9023==by 0x218B25: dispose (xmap.h:107) ==9023==by 0x218B25: xmap_p::~xmap_p() (xmap.h:112) ==9023==by 0x6224160: __run_exit_handlers (exit.c:108) ==9023==by 0x6224259: exit (exit.c:139) ==9023==by 0x6202BFD: (below main) (libc-start.c:344) ==9023== Block was alloc'd at ==9023==at 0x4C3217F: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==9023==by 0x218A09: RateLimit::init(RateLimit::level_e, char const*) (RateLimit.cc:55) ==9023==by 0x218A2C: RateLimit (RateLimit.h:52) ==9023==by 0x218A2C: RateLimit::init(RateLimit::level_e, char const*) (RateLimit.cc:55) ==9023==by 0x1ED1E2: Ftp::Do() (ftpclass.cc:2337) ==9023==by 0x1A97C4: SMTask::ScheduleThis() (SMTask.cc:209) ==9023==by 0x1A99D0: SMTask::Schedule() (SMTask.cc:248) ==9023==by 0x16614C: Job::WaitDone() (Job.cc:557) ==9023==by 0x15CBE3: main (lftp.cc:590) ==9023== ==9023== Invalid read of size 8 ==9023==at 0x2184B5: AddXfer (RateLimit.cc:31) ==9023==by 0x2184B5: RateLimit::~RateLimit() (RateLimit.cc:63) ==9023==by 0x218B18: dispose (xmap.h:107) ==9023==by 0x218B18: xmap_p::~xmap_p() (xmap.h:112) ==9023==by 0x6224160: __run_exit_handlers (exit.c:108) ==9023==by 0x6224259: exit (exit.c:139) ==9023==by 0x6202BFD: (below main) (libc-start.c:344) ==9023== Address 0x8072548 is 8 bytes inside a block of size 88 free'd ==9023==at 0x4C3323B: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==9023==by 0x218B25: dispose (xmap.h:107) ==9023==by 0x218B25: xmap_p::~xmap_p() (xmap.h:112) ==9023==by 0x6224160: __run_exit_handlers (exit.c:108) ==9023==by 0x6224259: exit (exit.c:139) ==9023==by 0x6202BFD: (below main) (libc-start.c:344) ==9023== Block was alloc'd at ==9023==at 0x4C3217F: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==9023==by 0x218A09: RateLimit::init(RateLimit::level_e, char const*) (RateLimit.cc:55) ==9023==by 0x218A2C: RateLimit (RateLimit.h:52) ==9023==by 0x218A2C: RateLimit::init(RateLimit::level_e, char const*) (RateLimit.cc:55) ==9023==by 0x1ED1E2: Ftp::Do() (ftpclass.cc:2337) ==9023==by 0x1A97C4: SMTask::ScheduleThis() (SMTask.cc:209) ==9023==by 0x1A99D0: SMTask::Schedule() (SMTask.cc:248) ==9023==by 0x16614C: Job::WaitDone() (Job.cc:557) ==9023==by 0x15CBE3: main (lftp.cc:590) ==9023== ==9023== ==9023== HEAP SUMMARY: ==9023== in use at exit: 41,827 bytes in 845 blocks ==9023== total heap usage: 4,439 allocs, 3,594 frees, 1,067,188 bytes allocated ==9023== ==9023== LEAK SUMMARY: ==9023==definitely lost: 144 bytes in 9 blocks ==9023==indirectly lost: 13 bytes in 1 blocks ==9023== possibly lost: 3,026 bytes in 39 blocks ==9023==still reachable: 38,644 bytes in 796 blocks ==9023== suppressed: 0 bytes in 0 blocks ==9023== Rerun with --leak-check=full to see details of leaked memory ==9023== ==9023== For counts of detected and suppressed errors, rerun with: -v ==9023== ERROR SUMMARY: 3 errors from 2 contexts (suppressed: 0 from 0) Seems like one of the various core dumps on exit fixed in l
[Desktop-packages] [Bug 1903089] [NEW] xserver-xorg-input-libinput don't work correctly
Public bug reported: When I use the mouse memory buffer, when I press the left mouse button, the buffer is erased in the programs of Mousepad and LO Writer. In LO calc and web-browser this function works fine, for example. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg-input-libinput 0.30.0-1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 5 19:45:59 2020 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu InstallationDate: Installed on 2020-09-19 (46 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200914) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b51d Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 03f0:a407 HP, Inc Wireless Optical Comfort Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 840 G3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p6 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.release: 1.42 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.42 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.78 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.120 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.42:bd08/19/2019:br1.42:efr133.120:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.78:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: X1X36UP#AK8 dmi.sys.vendor: HP 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug has-workaround hirsute reproducible ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1903089 Title: xserver-xorg-input-libinput don't work correctly Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: When I use the mouse memory buffer, when I press the left mouse button, the buffer is erased in the programs of Mousepad and LO Writer. In LO calc and web-browser this function works fine, for example. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg-input-libinput 0.30.0-1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 5 19:45:59 2020 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu InstallationDate: Installed on 2020-09-19 (46 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200914) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b51d Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 03f0:a407 HP, Inc Wireless Optical Comfort Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 840 G3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p6 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.release: 1.42 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.42 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.78 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.120 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.42:bd08/19/2019:br1.42:efr133.120:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.78:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: X1X36UP#AK8 dmi.sys.vendor: HP 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 N/A version.xserver-xorg-core
[Desktop-packages] [Bug 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
I use this small script based on Giuseppe's findings as a workaround: #!/bin/bash sudo modprobe -r snd_rn_pci_acp3x systemctl --user restart pulseaudio sudo modprobe snd_rn_pci_acp3x -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE 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.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1902918] Re: GDM crashes after upgrade to 20.10 due to apparmor and snap
Sure - please find attached my output of 'journalctl -b 0' - see file '2020-11-05 journalctl.txt' ** Attachment added: "2020-11-05 journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902918/+attachment/5431569/+files/2020-11-05%20journalctl.txt -- 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/1902918 Title: GDM crashes after upgrade to 20.10 due to apparmor and snap Status in gnome-shell package in Ubuntu: Incomplete Bug description: Releases: - Ubuntu 20.10 running Wayland - apparmor 3.0.0-0ubuntu1 Error description: After upgrading from Ubuntu 20.04 to 20.10 my GDM crashes regularly even without user interaction when the computer is left unused. After the crash the purple login screen shows and all open programs have been terminated (and unsaved data is lost). dmesg reveals that the issue is related to the "Ubuntu Software" Snap application in conjunction with apparmor. Probably the issue occurs when Ubuntu Software app is checking for updates in the background - hence it occurs without user interaction. Further information: The issue has also been described by other users: - https://askubuntu.com/questions/1230654/ubuntu-20-04-rebooting-and-freezing - https://www.dell.com/community/XPS/Ubuntu-20-04-XPS-13-crashes-and-logs-me-out/td-p/7623758 I attached the dmesg output Best regards, Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902918/+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 1890365] Re: [snap] Web Serial fails to access local device
That's right, snaps run sandboxed, so what matters is not device access
on the host, but what the snapd sandbox allows. Strictly speaking this
is not an Ubuntu-specific bug, because snaps run on other linux
distributions. This is definitely a snap-specific issue, which won't
affect the version of the RedHat chromium package.
What is the output of `snap connections chromium | grep raw-usb` ? The
third column should be ":raw-usb".
If it isn't, then run `snap connect chromium:raw-usb`.
When it is connected, then please run the steps in comment #1 to collect
updated output from the system journal?
--
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/1890365
Title:
[snap] Web Serial fails to access local device
Status in chromium-browser package in Ubuntu:
New
Bug description:
A javascript-based web page works fine when accessed through Chrome,
fails to recognize that any devices exist when accessed from Chromium
on the same Unubtu 20.04 platform.
The code includes the following snippet:
const requestOptions = {
filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();
Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
is listed in the pop-up, is selectable, and can communicate. Under
Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
contains only "No compatible devices found" message.
Experimental Web Features flag is enabled in both browsers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+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 1902915] Re: (Snap) Cannot add an attachment to the message
Here's the output of $ journalctl -f -- Logs begin at Fri 2020-03-13 14:32:21 CET. -- Nov 05 17:14:30 main systemd[1]: Starting Hostname Service... Nov 05 17:14:30 main dbus-daemon[1100]: [system] Successfully activated service 'org.freedesktop.hostname1' Nov 05 17:14:30 main systemd[1]: Started Hostname Service. Nov 05 17:15:00 main systemd[1]: systemd-hostnamed.service: Succeeded. Nov 05 17:15:01 main CRON[12883]: pam_unix(cron:session): session opened for user root by (uid=0) Nov 05 17:15:01 main CRON[12884]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Nov 05 17:15:01 main CRON[12883]: pam_unix(cron:session): session closed for user root Nov 05 17:17:01 main CRON[12921]: pam_unix(cron:session): session opened for user root by (uid=0) Nov 05 17:17:01 main CRON[12922]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 05 17:17:01 main CRON[12921]: pam_unix(cron:session): session closed for user root Nov 05 17:17:36 main audit[3814]: AVC apparmor="DENIED" operation="open" profile="snap.thunderbird.thunderbird" name="/etc/fstab" pid=3814 comm="thunderbird-bin" requested_mask="r" denied_mask="r" fsuid=1004 ouid=0 Nov 05 17:17:36 main kernel: audit: type=1400 audit(1604593056.015:61): apparmor="DENIED" operation="open" profile="snap.thunderbird.thunderbird" name="/etc/fstab" pid=3814 comm="thunderbird-bin" requested_mask="r" denied_mask="r" fsuid=1004 ouid=0 Nov 05 17:17:36 main kernel: audit: type=1400 audit(1604593056.015:62): apparmor="DENIED" operation="open" profile="snap.thunderbird.thunderbird" name="/run/mount/utab" pid=3814 comm="thunderbird-bin" requested_mask="r" denied_mask="r" fsuid=1004 ouid=0 Nov 05 17:17:36 main audit[3814]: AVC apparmor="DENIED" operation="open" profile="snap.thunderbird.thunderbird" name="/run/mount/utab" pid=3814 comm="thunderbird-bin" requested_mask="r" denied_mask="r" fsuid=1004 ouid=0 Nov 05 17:17:36 main dbus-daemon[1100]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.481' (uid=1004 pid=3814 comm="/snap/thunderbird/92/thunderbird-bin " label="snap.thunderbird.thunderbird (enforce)") Nov 05 17:17:36 main audit[3814]: AVC apparmor="DENIED" operation="open" profile="snap.thunderbird.thunderbird" name="/run/mount/utab" pid=3814 comm="thunderbird-bin" requested_mask="r" denied_mask="r" fsuid=1004 ouid=0 Nov 05 17:17:36 main kernel: audit: type=1400 audit(1604593056.063:63): apparmor="DENIED" operation="open" profile="snap.thunderbird.thunderbird" name="/run/mount/utab" pid=3814 comm="thunderbird-bin" requested_mask="r" denied_mask="r" fsuid=1004 ouid=0 Nov 05 17:17:36 main systemd[1]: Starting Hostname Service... Nov 05 17:17:36 main dbus-daemon[1100]: [system] Successfully activated service 'org.freedesktop.hostname1' Nov 05 17:17:36 main systemd[1]: Started Hostname Service. Nov 05 17:17:36 main audit[1100]: USER_AVC pid=1100 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.482" pid=3814 label="snap.thunderbird.thunderbird" peer_pid=13041 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? terminal=?' Nov 05 17:17:36 main kernel: audit: type=1107 audit(1604593056.107:64): pid=1100 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.482" pid=3814 label="snap.thunderbird.thunderbird" peer_pid=13041 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? terminal=?' Nov 05 17:17:36 main kernel: audit: type=1107 audit(1604593056.107:65): pid=1100 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.482" pid=3814 label="snap.thunderbird.thunderbird" peer_pid=13041 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? terminal=?' Nov 05 17:17:36 main audit[1100]: USER_AVC pid=1100 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.482" pid=3814 label="snap.thunderbird.thunderbird" peer_pid=13041 peer_label="unconfined" And finally ... After installing xdg-desktop-portal-gtk the dialog appears. Maybe I'm missing something. It's a snap, can you explain why I need to install a debian package to get it working. Surely that's the whole point of snaps? -- You received this b
[Desktop-packages] [Bug 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup
@seb128 Thank you for the build in the ppa! Can you please publish the binaries so we can update pulseaudio the standard way? -- 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/1901922 Title: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW 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.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1901922/+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 1893300] Re: The status of cups still shows idle when the printer has been unplugged
hm, I would appreciate a bit more information in the Regression Potential section. In this section we need some analysis on where to look for regressions after this lands into the archive. This should be an exercise, thinking: "hmmm, if we change these parts of the code, what could go wrong? Where should we expect regressions, new bugs?" ** Changed in: system-config-printer (Ubuntu Groovy) Status: Fix Committed => Incomplete ** Changed in: system-config-printer (Ubuntu Focal) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged Status in OEM Priority Project: Triaged Status in OEM Priority Project focal series: New Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Focal: Incomplete Status in system-config-printer source package in Groovy: Incomplete Bug description: [ Impact ] After printers (non-ippusb protocal) have been disconnected, the status of cups still shows "idle" instead of "disabled", so seems the disconnected procedure hasn't worked well. [ Test Case ] 1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 20.04 machine 2. Wait for the status of cups became "Idle" (lpstat -p) 3. Unplug the cable of the printer 4. Check the status of cups again. (lpstat -p) [ Regression potential ] Low, the change just makes "strcmp" to "srtsrt" and has more checks on the existing of device path. [Expected result] The status should show disabled. [Actual result] The status shows idle. [info] Target: HP LaserJet Pro203dw HP Officejet 100 Mobile Printer HP Officeject 200 Mobile Printer Brother HL-2250DN Samsung ML-331x Upstream Bug: https://github.com/OpenPrinting/system-config- printer/issues/182 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup
I've uploaded the new version to hirsute and a groovy build in the ppa there https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/ -- 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/1901922 Title: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW 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.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1901922/+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 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
** Description changed: SRU request: [Impact] - * Installing the 340 driver will fail when running Linux 5.7 or newer. - + * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] - * Install nvidia-340 from -proposed. + * Install nvidia-340 from -proposed. - * Check that the modules was built and installed, using the -following command: + * Check that the modules was built and installed, using the + following command: -dkms status + dkms status [Regression Potential] - * Low, Groovy doesn't have a working driver. + * The driver once built and installed could be not working and lead to + have the desktop not starting for example. Check that you get a desktop + loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 source package in Groovy: In Progress Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
** Also affects: nvidia-graphics-drivers-340 (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Groovy) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Groovy) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Groovy) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Description changed: + SRU request: + + [Impact] + + * Installing the 340 driver will fail when running Linux 5.7 or newer. + + + [Test Case] + + * Install nvidia-340 from -proposed. + + * Check that the modules was built and installed, using the +following command: + +dkms status + + [Regression Potential] + + * Low, Groovy doesn't have a working driver. + + + Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 source package in Groovy: In Progress Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * Low, Groovy doesn't have a working driver. Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1890365] Re: [snap] Web Serial fails to access local device
I do not understand your comment, perhaps because I do not understand
snap.
/etc/udev/rules.d for this device configure it to be 666, and it works
fine under other browsers, so you are not talking about actual device
access, you are talking about the mapping of this real device onto some
virtual "raw-usb" device of the snap's sandbox ?
I did what you suggested, tried from the command line before and after
launching chromium. I had previously also turned off apparmor for
chromium altogether (comment #4). None of these affected the outcome.
So, please explain how I "ensure that said interface is connected" for
the purposes of the snap sandbox.
I can use chromium successfully for accessing the device under RedHat,
so this is specifically a Ubuntu/Chromium bug/misfeature.
--
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/1890365
Title:
[snap] Web Serial fails to access local device
Status in chromium-browser package in Ubuntu:
New
Bug description:
A javascript-based web page works fine when accessed through Chrome,
fails to recognize that any devices exist when accessed from Chromium
on the same Unubtu 20.04 platform.
The code includes the following snippet:
const requestOptions = {
filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();
Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
is listed in the pop-up, is selectable, and can communicate. Under
Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
contains only "No compatible devices found" message.
Experimental Web Features flag is enabled in both browsers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+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 1901196] Re: kernel module failed to build [ Bad return status for module build on kernel: 5.8.0-25-generic (x86_64)]
*** This bug is a duplicate of bug 1872950 *** https://bugs.launchpad.net/bugs/1872950 ** This bug is no longer a duplicate of bug 1896878 Doesn't compile for groovy ** This bug has been marked a duplicate of bug 1872950 Nvidia 340.108 fails to install with kernels 5.5 onward -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1901196 Title: kernel module failed to build [ Bad return status for module build on kernel: 5.8.0-25-generic (x86_64)] Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: While installing Nvidia-340 driver, I am getting the following error. Setting up nvidia-340 (340.108-0ubuntu5) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Removing old nvidia-340-340.108 DKMS files... Loading new nvidia-340-340.108 DKMS files... Building for 5.8.0-25-generic Building for architecture x86_64 Building initial module for 5.8.0-25-generic Error! Bad return status for module build on kernel: 5.8.0-25-generic (x86_64) Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information. dpkg: error processing package nvidia-340 (--configure): installed nvidia-340 package post-installation script subprocess returned error exit status 10 Processing triggers for libc-bin (2.32-0ubuntu3) ... Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-25-generic Errors were encountered while processing: nvidia-340 E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1901196/+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 1899731] Re: [SRU] Backport button metric changes from groovy to focal
Marking as fix released since it's not impacting the current serie, a target for focal is going to be added once the SRU is accepted ** Changed in: yaru-theme (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1899731 Title: [SRU] Backport button metric changes from groovy to focal Status in yaru-theme package in Ubuntu: Fix Released Bug description: [Impact] * Focal users will soon have their yaru themes mismatched in snaps and debs * yaru-theme-gtk includes changes for button sizes in groovy, gtk- common-themes will be updated with the updated yaru-theme-gtk so groovies debs and snaps look consistent but this will leave focal deb and snaps incosistent, so focals debs also need an update. * Backporting the yaru gtk theme from groovy to focal will fix this, the SHELL theme (yaru-theme-gnome-shell) however should NOT be backported, because the gnome shell version is different and thus the JavaScript components of gnome-shell would then not match the theme any more. The icon theme however, can also be backported if wanted [Test Case] * Update gtk-common-themes from https://gitlab.gnome.org/Community/Ubuntu/gtk-common- themes/-/jobs/951794/artifacts/browse in focal and see how gtk debs like nautilus look different in button sizing than snap-store aka ubuntu software [Regression Potential] * no regression potential unless the gnome shell theme is also backported which should NOT happen [Other Info] * The updates were necessary for groovy, because having gtk3 themes with different button sizes than adwaita creates issues with sizes, see https://github.com/ubuntu/yaru/pull/2361 for further issues linked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1899731/+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 1901071] Re: package nvidia-340 340.108-0ubuntu5 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 10
*** This bug is a duplicate of bug 1872950 *** https://bugs.launchpad.net/bugs/1872950 ** This bug is no longer a duplicate of bug 1896878 Doesn't compile for groovy ** This bug has been marked a duplicate of bug 1872950 Nvidia 340.108 fails to install with kernels 5.5 onward -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1901071 Title: package nvidia-340 340.108-0ubuntu5 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Is nvidia-340-108 supported? ProblemType: Package DistroRelease: Ubuntu 20.10 Package: nvidia-340 340.108-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.452 Date: Thu Oct 22 17:05:19 2020 ErrorMessage: installed nvidia-340 package post-installation script subprocess returned error exit status 10 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 340.108-0ubuntu5 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1901071/+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 1896878] Re: Doesn't compile for groovy
*** This bug is a duplicate of bug 1872950 *** https://bugs.launchpad.net/bugs/1872950 ** This bug has been marked a duplicate of bug 1872950 Nvidia 340.108 fails to install with kernels 5.5 onward -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1896878 Title: Doesn't compile for groovy Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: dkms.conf can be changed to just use PATCH[0]="kernel-5.7.patch" PATCH[1]="buildfix_kernel_5.8.patch" with patches from archlinux: https://aur.archlinux.org/cgit/aur.git/tree/buildfix_kernel_5.8.patch?h=nvidia-340xx and https://gitlab.manjaro.org/packages/extra/linux57-extramodules/nvidia-340xx/-/raw/master/kernel-5.7.patch?inline=false Except that the kernel-5.7 patch needs to be modified to remove the dkms.conf section therein, and the kernel/ paths for files needs to be removed. A fixed kernel-5.7.patch file is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+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 1901493] Re: fails to build on groovy [ERROR: Kernel configuration is invalid.]
*** This bug is a duplicate of bug 1872950 *** https://bugs.launchpad.net/bugs/1872950 ** This bug is no longer a duplicate of bug 1896878 Doesn't compile for groovy ** This bug has been marked a duplicate of bug 1872950 Nvidia 340.108 fails to install with kernels 5.5 onward -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1901493 Title: fails to build on groovy [ERROR: Kernel configuration is invalid.] Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: nvidia-340 fails to build after update to 20.10. Attaching crash log. Note: This is fatal on the Thinkpad T61. Desktop does not start. apt-cache policy nvidia-340 nvidia-340: Installiert: (keine) Installationskandidat: 340.108-0ubuntu5 Versionstabelle: 340.108-0ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu groovy/restricted amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 09:38:20 2020 InstallationDate: Installed on 2020-07-12 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to groovy on 2020-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1901493/+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 1902485] Re: New upstream release 13.99.3
** Changed in: pulseaudio (Ubuntu) Status: In Progress => Fix Committed -- 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/1902485 Title: New upstream release 13.99.3 Status in pulseaudio package in Ubuntu: Fix Committed Bug description: New upstream release 13.99.3 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/tags/v13.99.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902485/+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 1900255] Re: accountsservice drop privileges denial of service (GHSL-2020-187, GHSL-2020-188)
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1900255
Title:
accountsservice drop privileges denial of service (GHSL-2020-187,
GHSL-2020-188)
Status in accountsservice package in Ubuntu:
Fix Released
Bug description:
# GitHub Security Lab (GHSL) Vulnerability Report: `GHSL-2020-187`,
`GHSL-2020-188`
The [GitHub Security Lab](https://securitylab.github.com) team has
identified potential security vulnerabilities in
[accountsservice](https://git.launchpad.net/ubuntu/+source/accountsservice/).
We are committed to working with you to help resolve these issues. In
this report you will find everything you need to effectively
coordinate a resolution of these issues with the GHSL team.
If at any point you have concerns or questions about this process,
please do not hesitate to reach out to us at `security...@github.com`
(please include `GHSL-2020-187` or `GHSL-2020-188` as a reference).
If you are _NOT_ the correct point of contact for this report, please
let us know!
## Summary
The accountsservice daemon drops privileges to perform certain
operations. For example while performing the
`org.freedesktop.Accounts.User.SetLanguage` D-Bus method, which can be
triggered by an unprivileged user, accounts-daemon temporarily drops
privileges to the same UID as the user, to avoid being tricked into
opening a file which the unprivileged user should not be able to
access. Unfortunately, by changing its
[RUID](https://en.wikipedia.org/wiki/User_identifier#Real_user_ID) it
has given the user permission to send it signals. This means that the
unprivileged user can send accounts-daemon a `SIGSTOP` signal, which
stops the process and causes a denial of service.
## Product
[accountsservice](https://git.launchpad.net/ubuntu/+source/accountsservice/)
## Tested Version
* accountsservice, version 0.6.55-0ubuntu12~20.04.1
* Tested on Ubuntu 20.04.1 LTS
Note: I believe these issues only exist in Ubuntu's version of
accountsservice. I couldn't find the vulnerable functions in the git
repos maintained by
[freedesktop](https://gitlab.freedesktop.org/accountsservice/accountsservice)
or [debian](https://salsa.debian.org/freedesktop-
team/accountsservice). I originally discovered the vulnerable code in
the version of the code that I had obtained by running `apt-get source
accountsservice`, but I struggled to figure out where it came from
when I started searching the official repositories. I eventually
tracked it down to this patch file: [0010-set-
language.patch](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010
-set-language.patch?h=ubuntu/focal-
updates&id=e0347185d4c5554b026c13ccca691577c239afd5).
## Details
### Issue 1: accountsservice drop privileges `SIGSTOP` denial of
service (`GHSL-2020-187`)
A [source code
patch](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010
-set-language.patch?h=ubuntu/focal-
updates&id=e0347185d4c5554b026c13ccca691577c239afd5) that (as far as I
know) only exists in Ubuntu's version of accountsservice, adds a
function named
[`user_drop_privileges_to_user`](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010
-set-language.patch?h=ubuntu/focal-
updates&id=e0347185d4c5554b026c13ccca691577c239afd5#n66):
```c
static gboolean
user_drop_privileges_to_user (User *user)
{
if (setresgid (user->gid, user->gid, -1) != 0) {
g_warning ("setresgid() failed");
return FALSE;
}
if (setresuid (accounts_user_get_uid (ACCOUNTS_USER (user)),
accounts_user_get_uid (ACCOUNTS_USER (user)), -1) != 0) {
g_warning ("setresuid() failed");
return FALSE;
}
return TRUE;
}
```
This function is used to drop privileges while doing operations on
behalf of an unprivileged user. Dropping the
[EUID](https://en.wikipedia.org/wiki/User_identifier#Effective_user_ID)
is a sensible precaution, which prevents accountsservice from
accessing a file which the unprivileged user cannot access themselves.
Unfortunately, dropping the
[RUID](https://en.wikipedia.org/wiki/User_identifier#Real_user_ID) has
the opposite effect of making security worse, because it enables the
unprivileged user to send signals to accountsservice. For example,
they can send a `SIGSTOP` which stops the accountsservice daemon and
causes a denial of service.
The vulnerability can be triggered via multiple different D-Bus
methods. Many of them involve precise timing to send the `SIGSTOP`
signal at just the right moment. But there is a much simpler and more
reliable way to reproduce the vulnerability by combining th
[Desktop-packages] [Bug 1902900] Re: Workspaces menu flashes when moving between workspace A and workspace B having B Firefox with a video in full screen on it
** Changed in: firefox (Ubuntu) Status: Incomplete => New -- 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/1902900 Title: Workspaces menu flashes when moving between workspace A and workspace B having B Firefox with a video in full screen on it Status in firefox package in Ubuntu: New Bug description: As I said in the title the menu with the 3 workspaces flashes if you switch from a normal workspace to a workspace that has a fullscreen video in Firefox. How to reproduce * Open Firefox * Open a video in full screen (I tested prime video and twitch) * Press and keep pressed ctrl-alt and arrow to move between workspaces * When you reach the video workspaces still keep pressed ctrl-alt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 82.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: wl AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sibilant 2096 F pulseaudio BuildID: 20201014125134 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 16:28:48 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:361 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-11-03 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.92 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/firefox/omni.ja:greprefs.js:361 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=82.0/20201014125134 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 232.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr232.0.0.0.0:bd04/12/2020:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1902900/+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 1902749] Re: [amdgpu] Log in screen flashes on and off until I log in
Also, when the laptop enters sleep mode after being inactive for a while the screen flashes the same way, even on the desktop after i log in. This can be fixed by changing the screen's refresh rate from 120hz to 48hz and then back to 120hz. -- 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/1902749 Title: [amdgpu] Log in screen flashes on and off until I log in Status in mutter package in Ubuntu: Incomplete Bug description: Im on Ubuntu 20.04.1 with an AMD Ryzen 7 4800h CPU and a Nvidia GTX 1650ti [Mobile] GPU using nvidia-driver-450 Kernel is up to date (5.9.3) When my laptop boots, the log in screen flashes black and quickly back on until i log in. When i reach the desktop the flashing stops. Still, having the screen flickering on the log in screen is very annoying. As far as i can tell, the laptop doesn't have any further screen issues. Thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.9.3-050903-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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) 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 17:46:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU116M [GeForce GTX 1650 Ti Mobile] [10de:2192] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited Device [1d05:1101] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited Renoir [1d05:1100] InstallationDate: Installed on 2020-10-27 (7 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Standard GK5NPFO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.3-050903-generic root=UUID=a7144690-52e4-4688-a61a-b208b0648077 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.16PCS01 dmi.board.asset.tag: Standard dmi.board.name: GK5NPFO dmi.board.vendor: TongFang dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: Standard dmi.chassis.version: Standard dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.16PCS01:bd09/01/2020:br5.16:efr1.22:svnStandard:pnGK5NPFO:pvrStandard:rvnTongFang:rnGK5NPFO:rvrStandard:cvnStandard:ct10:cvrStandard: dmi.product.family: Standard dmi.product.name: GK5NPFO dmi.product.sku: 0001 dmi.product.version: Standard dmi.sys.vendor: Standard version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/mutter/+bug/1902749/+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 1902900] Re: Workspaces menu flashes when moving between workspace A and workspace B having B Firefox with a video in full screen on it
I can confirm that I'm using X11 and that the problem occurs only when using Firefox, with chromium everything works as expected. -- 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/1902900 Title: Workspaces menu flashes when moving between workspace A and workspace B having B Firefox with a video in full screen on it Status in firefox package in Ubuntu: Incomplete Bug description: As I said in the title the menu with the 3 workspaces flashes if you switch from a normal workspace to a workspace that has a fullscreen video in Firefox. How to reproduce * Open Firefox * Open a video in full screen (I tested prime video and twitch) * Press and keep pressed ctrl-alt and arrow to move between workspaces * When you reach the video workspaces still keep pressed ctrl-alt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 82.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: wl AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sibilant 2096 F pulseaudio BuildID: 20201014125134 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 16:28:48 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:361 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-11-03 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.92 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/firefox/omni.ja:greprefs.js:361 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=82.0/20201014125134 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 232.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr232.0.0.0.0:bd04/12/2020:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1902900/+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 1902918] Re: GDM crashes after upgrade to 20.10 due to apparmor and snap
Could you add the 'journalctl -b 0' log from the system after triggering the issue? -- 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/1902918 Title: GDM crashes after upgrade to 20.10 due to apparmor and snap Status in gnome-shell package in Ubuntu: Incomplete Bug description: Releases: - Ubuntu 20.10 running Wayland - apparmor 3.0.0-0ubuntu1 Error description: After upgrading from Ubuntu 20.04 to 20.10 my GDM crashes regularly even without user interaction when the computer is left unused. After the crash the purple login screen shows and all open programs have been terminated (and unsaved data is lost). dmesg reveals that the issue is related to the "Ubuntu Software" Snap application in conjunction with apparmor. Probably the issue occurs when Ubuntu Software app is checking for updates in the background - hence it occurs without user interaction. Further information: The issue has also been described by other users: - https://askubuntu.com/questions/1230654/ubuntu-20-04-rebooting-and-freezing - https://www.dell.com/community/XPS/Ubuntu-20-04-XPS-13-crashes-and-logs-me-out/td-p/7623758 I attached the dmesg output Best regards, Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902918/+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 1902485] Re: New upstream release 13.99.3
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- 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/1902485 Title: New upstream release 13.99.3 Status in pulseaudio package in Ubuntu: In Progress Bug description: New upstream release 13.99.3 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/tags/v13.99.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902485/+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 1902918] Re: GDM crashes after upgrade to 20.10 due to apparmor and snap
Thanks for your hints on how to get the crash logs. My laptop crashed a few more times this morning so I had sufficient opportunity to get logs. Unfortunately Ubuntu is not creating any logs under "/var/crash" neither online (step 2) when this issue occurs (I can however see other log files so generally it works). As you pointed out in step 3 I commented out the related line in my "/etc/apport/crashdb.conf" file but it is still not logging anything there. If you could point me to other log files in addition to the dmesg and journalctl which I posted in the ticket I am happy to add them. -- 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/1902918 Title: GDM crashes after upgrade to 20.10 due to apparmor and snap Status in gnome-shell package in Ubuntu: Incomplete Bug description: Releases: - Ubuntu 20.10 running Wayland - apparmor 3.0.0-0ubuntu1 Error description: After upgrading from Ubuntu 20.04 to 20.10 my GDM crashes regularly even without user interaction when the computer is left unused. After the crash the purple login screen shows and all open programs have been terminated (and unsaved data is lost). dmesg reveals that the issue is related to the "Ubuntu Software" Snap application in conjunction with apparmor. Probably the issue occurs when Ubuntu Software app is checking for updates in the background - hence it occurs without user interaction. Further information: The issue has also been described by other users: - https://askubuntu.com/questions/1230654/ubuntu-20-04-rebooting-and-freezing - https://www.dell.com/community/XPS/Ubuntu-20-04-XPS-13-crashes-and-logs-me-out/td-p/7623758 I attached the dmesg output Best regards, Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902918/+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 1901413] Re: Sound Blaster Audigy 5/Rx cannot be configured as input/output
Should be fixed by a new PulseAudio profile: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/460d0c0b79939e4e43f30824bcd6358feb1727f5 ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: New Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+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 1902969] Re: Thunder freezes UI when changing from title bars to CSD
Could you add the 'journalctl -b 0' log from the system after getting the issue? Reassigning to gnome-shell since that's where the lock is (could be due to the dock extension though) ** Package changed: thunderbird (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Low => High ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Summary changed: - Thunder freezes UI when changing from title bars to CSD + desktop freezes when changing thundebird win decorations -- 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/1902969 Title: desktop freezes when changing thundebird win decorations Status in gnome-shell package in Ubuntu: New Bug description: I noticed a bug. In Thunderbird (deb or snap) version open and right click on the tab bar and choose customization and mess around with showing title or not and close out of it the icon for TB is still in the dock. If you click on the icon it locks up the UI. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.3.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mram 2160 F pulseaudio /dev/snd/controlC0: mram 2160 F pulseaudio BuildID: 20201006011220 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 18:55:14 2020 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-10-04 (31 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.45 metric 100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.0/20200629202523 (Out of date) Profile0 (Default) - LastVersion=78.3.2/20201006011220 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.release: 4.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AGH6120H.86A.0015.2012.0926.1822 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61AGL dmi.board.vendor: Intel Corporation dmi.board.version: G71256-202 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: sabc1 dmi.modalias: dmi:bvnIntelCorp.:bvrAGH6120H.86A.0015.2012.0926.1822:bd09/26/2012:br4.6:svnSystem76,Inc.:pnSableComplete:pvrsabc1:rvnIntelCorporation:rnDH61AGL:rvrG71256-202:cvnSystem76,Inc.:ct3:cvrsabc1: dmi.product.family: To be filled by O.E.M. dmi.product.name: Sable Complete dmi.product.sku: To be filled by O.E.M. dmi.product.version: sabc1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902969/+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 1903048] [NEW] Bluetooth won't activate on the pi 400
Public bug reported: The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. ** Affects: bluez (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: New ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: New Bug description: The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash
*** This bug is a duplicate of bug 1890394 *** https://bugs.launchpad.net/bugs/1890394 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1902871 Title: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash Status in lightdm package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: Reproduction : take a bog-standard system with Intel CPU and Intel graphics (mobo like Foxconn 45GM/45CM/45CM-S or ECS 945GCT-M2 with Intel E4500, or ASRock G41C-VS/G41M-VS3/G31M-S with Intel E3300/E3400, or Asrock P4I45GL with Intel Pentium4 2.40GHz) ; install Lubuntu 18.04 i386 on it ; install all latest upgrades including systemd packages of version 237-3ubuntu10.43 ; reboot and watch black screen with blinking text cursor Fix : switch into text console or log in as sudo-capable user over the network look at lightdm crashes in dmesg download past version of systemd packages (237-3ubuntu10.42) install them by dpkg reboot and enjoy your graphic screen again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1902871/+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
