[Desktop-packages] [Bug 124406] Re: Keyboard keys get stuck and repeat
Still happens on Ubuntu 20.04 with a Lenovo ThinkPad L14 Gen 2 (and the proposed OEM kernel). Workaround/fix for the issue is plugging in a USB keyboard. After that the issue is gone and the external keyboard can be unplugged again, -- 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/124406 Title: Keyboard keys get stuck and repeat Status in GNU Emacs: Invalid Status in Linux: Confirmed Status in X.Org X server: In Progress Status in linux package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Status in linux source package in Jaunty: Won't Fix Status in xorg-server source package in Jaunty: Invalid Status in Gentoo Linux: New Bug description: Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often get 'stuck' and continue being 'clicked' even after they are physically released. For example when clicking Alt-F4, sometimes it gets stuck so all the windows are closed instead of just one. My configuration is Feisty + Xgl + Compiz Fusion. My previous configuration was Edgy + Xgl + Beryl, where this didn't happen. Others have reported the same problem without using either Xgl or Compiz. The keyboard itself isn't the problem. When dual-booting to Windows, everything works fine. Also, the problem happens with two different keyboards (internal laptop, external USB). My best guess is that the problem occurs at time of high system load. Somehow during these times the key-release signal gets lost and the key-press is repeated indefinitely. This happens more often with Compiz configurations because Compiz tends to increase system load. It also happens more often with power-hungry apps like Firefox and Acrobat Reader for similar reasons. PS: When the keys would repeat all input devices would be locked up. ie. mouse won't move, clicks don't do anything, keyboard presses don't register. Then when it becomes unstuck, the mouse moves around and everything. Hope this helps. See also this forum thread for other people with the same problem: http://ubuntuforums.org/showthread.php?t=432057 To manage notifications about this bug go to: https://bugs.launchpad.net/emacs/+bug/124406/+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 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP
We have at least one Ubuntu installation that was updated from 18.04 to 20.04 with the automatic transition to chromium in snap on channel stable. Every now and then chromium tabs crash with the SIGTRAP error. Possible workarounds are: * Restarting chromium, or (if this doesn't work) * Restart the complete laptop Please give details on how to collect log or debug data and where/how to post them here (just uploading files, using an Ubuntu command?) -- 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/1914918 Title: The snap being updated in the background causes both old and new tabs to die to SIGTRAP Status in chromium-browser package in Ubuntu: Confirmed Bug description: The last few background updates of chromium have made some old tabs suddenly crash with SIGTRAP and it also makes it impossible to open new tabs, those die instantly with a SIGTRAP as well. This is incredibly destructive to whatever might be the dying tabs' unsaved state and there's no warning about it. Yet again a snap- related change rolled out to users with absolutely amateur-tier testing. Ubuntu: 20.04.2 Snap: 2.48+20.04 Chromium: 88.0.4324.150 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+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 1905010] Re: [snap] chromium forgets custom root certificates after each update
One workaround seems to be saving the chromium profile, deleting the
profile, restarting chromium and then move the saved profile back into
place.
I could now add our internal root CA without a problem. Will have a look
how chromium behaves with the next snap update.
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
Expired
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 1905010] Re: [snap] chromium forgets custom root certificates after each update
We have another case where Chromium "forgets" our internal root CA but
tells me it is already installed.
I can pinpoint this a bit further: we did an upgrade fom 18.04 to 20.04.
Uninstalling and re-installing chromium with snap seems to solve the
problem in most cases.
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
Expired
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 1905010] Re: [snap] chromium forgets custom root certificates after each update
We do not have any customizations in Chromium, so I assume they are
saved in the default location.
When rolling out our clients, we install our internal CA to
/etc/univention/ssl/ucsCA/CAcert.pem with a symlink in /usr/local/share
/ca-certificates/UCSdomain.crt:
0 lrwxrwxrwx 1 root root 36 Jan 17 2019 UCSdomain.crt ->
/etc/univention/ssl/ucsCA/CAcert.pem
and then "sudo update-ca-certificates" to include it to Ubuntu's SSL
storage. But that was ignored by Chromium since ever.
Interestingly, when I want to add our CA to Chromium, an error message
pops up, informing me about being unable to install the certificate to
Chromium since it's already installed - but I cannot find the
certificate in the overview.
Interstingly, cert9.db was not updated two days ago when I reproduced
the error for the appreport:
cd snap/chromium/current/.pki/nssdb
insgesamt 69.632
28.672 -rw--- 1 tdenisse Domain Users 28.672 Mai 8 2020 cert9.db
36.864 -rw--- 1 tdenisse Domain Users 36.864 Mai 8 2020 key4.db
4.096 -rw--- 1 tdenisse Domain Users468 Apr 30 2020 pkcs11.txt
I just made a clean re-install of Chromium (uninstalled Debian and snap
package, moved ~/snap/chromium to chromium_old, reinstalled Debian and
snap package), installed our certificate and now everything works
(again). I will keep you updated with the next chromium update through
snap.
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
[Desktop-packages] [Bug 1905010] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437201/+files/Lspci-vt.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help
[Desktop-packages] [Bug 1905010] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437206/+files/ProcCpuinfoMinimal.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1905010] Snap.Info.chromium.txt
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437212/+files/Snap.Info.chromium.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1905010] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437208/+files/ProcInterrupts.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1905010] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437200/+files/Lspci.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help :
[Desktop-packages] [Bug 1905010] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437217/+files/acpidump.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help
[Desktop-packages] [Bug 1905010] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437216/+files/UdevDb.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help :
[Desktop-packages] [Bug 1905010] Re: [snap] chromium forgets custom root certificates after each update
apport information
** Tags added: apport-collected focal snap
** Description changed:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is deleted
from the certificate storage, leading to all our internal websites being
marked as potentially evil.
- It would be nice if either snap migrates all data completely from one
- version to another, or saving custom certificates inside the current-
- symlink (which does not forget any data stored in there)
+ It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.12
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DRM.card0-DP-1:
+ enabled: enabled
+ dpms: On
+ status: connected
+ edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
+ modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
+ DRM.card0-DP-2:
+ enabled: disabled
+ dpms: Off
+ status: disconnected
+ edid-base64:
+ modes:
+ DRM.card0-HDMI-A-1:
+ enabled: disabled
+ dpms: Off
+ status: disconnected
+ edid-base64:
+ modes:
+ DRM.card0-HDMI-A-2:
+ enabled: disabled
+ dpms: Off
+ status: disconnected
+ edid-base64:
+ modes:
+ DRM.card0-eDP-1:
+ enabled: disabled
+ dpms: Off
+ status: connected
+ edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
+ modes: 1920x1080
+ DiskUsage:
+ Filesystem Type Size Used Avail Use% Mounted on
+ /dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
+ tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
+ /dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2019-01-17 (675 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ MachineType: LENOVO 20LS001AGE
+ Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
+ Snap.Changes:
+ ID Status Spawn Ready Summary
+ 186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
+ 187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
+ Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
+ Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
+ Tags: focal snap
+ Uname: Linux 5.4.0-54-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
+ UserGroups: dialout lpadmin sambashare sudo wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 12/18/2019
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: R0QET60W (1.37 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20LS001AGE
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40697 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad L480
+ dmi.product.name: 20LS001AGE
+ dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
+ dmi.product.version: ThinkPad L480
+ dmi.sys.vendor: LENOVO
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437198/+files/CurrentDmesg.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
[Desktop-packages] [Bug 1905010] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437205/+files/ProcCpuinfo.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1905010] Snap.Info.gtk-common-themes.txt
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437215/+files/Snap.Info.gtk-common-themes.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1905010] Snap.Info.core18.txt
apport information
** Attachment added: "Snap.Info.core18.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437214/+files/Snap.Info.core18.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1905010] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437209/+files/ProcModules.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1905010] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437203/+files/Lsusb-t.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help
[Desktop-packages] [Bug 1905010] Snap.ChromiumPrefs.txt
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437210/+files/Snap.ChromiumPrefs.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1905010] Snap.Connections.txt
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437211/+files/Snap.Connections.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1905010] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437207/+files/ProcEnviron.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1905010] Snap.Info.core.txt
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437213/+files/Snap.Info.core.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1905010] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437204/+files/Lsusb-v.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help
[Desktop-packages] [Bug 1905010] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437202/+files/Lsusb.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help :
[Desktop-packages] [Bug 1905010] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1905010/+attachment/5437199/+files/Dependencies.txt
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
New
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1905010] [NEW] [snap] chromium forgets custom root certificates after each update
Public bug reported: Running lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 with snap list | grep chromium chromium 87.0.4280.661411 latest/stable canonical* - each time the snap container gets an update, our own root CA is deleted from the certificate storage, leading to all our internal websites being marked as potentially evil. It would be nice if either snap migrates all data completely from one version to another, or saving custom certificates inside the current- symlink (which does not forget any data stored in there) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1905010 Title: [snap] chromium forgets custom root certificates after each update Status in chromium-browser package in Ubuntu: New Bug description: Running lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 with snap list | grep chromium chromium 87.0.4280.661411 latest/stable canonical* - each time the snap container gets an update, our own root CA is deleted from the certificate storage, leading to all our internal websites being marked as potentially evil. It would be nice if either snap migrates all data completely from one version to another, or saving custom certificates inside the current- symlink (which does not forget any data stored in there) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work). Xorg crashes with SIGSEGV in ?? from _init() from xf86RandR12Init() from xf86C
So far, this issue did not occur using Ubuntu 20.04. I'll keep you up to date. -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work). Xorg crashes with SIGSEGV in ?? from _init() from xf86RandR12Init() from xf86CrtcScreenInit() Status in xorg-server package in Ubuntu: New Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
Plug your headset out and back in, confirm the headset is present in
ALSA but not pulseaudio and kill pulseaudio: pkill -U $USER pulseaudio.
Pulseaudio will restart itself automatically.
All audiostreams currently active will break, but pulseaudio is
restarted and should recognoze your headset again.
Also, this does not happen with Ubunutu 20.04 on my laptop (yet).
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in alsa-lib package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1865499/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
Quick update: the package updates from the proposed repository for
* libasound2-data,
* libasound2:amd64, and
* libasound2:i386
seemed to fixed the problems.
All affected USB headsets we use
* Logitech 960,
* SennHheiser PC8, and
* Plantronics Blackwire 3220
now are detected on every hot-plug.
When will the packages move from proposedto updates or security?
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
Got pulseaudio to stop auto-reloading with "autospawn = no" in
/etc/pulseaudio/client.conf.
Attached is the output from "pulseaudio -vv". the PLAYBACK stream is
recognized, but not the CAPTURE stream.
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
** Attachment added: "pulseaudio-vv"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+attachment/5334265/+files/pulseaudio-vv
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
I installed a fresh Ubuntu 18.04.3 and updated nearly every package one
by one (to name a few, pulseaudio, libasound, systemd, kernel (4.15,
later HWE 5.3) - all to no avail, up to a full upgrade of all packages
so now the system is 18.04.4. The problem is not reproducable with a
fresh and clean installation.
But we have a new case, the colleague got the auto security updates on
2020-03-02 and did a manual package update on 2020-03-04. After the
updates on 2020-03-04 the system was rebooted by the user, and now has
the same bug.
This affects both wired (USB) and wireless (bluetooth) headsets. As soon
as the headset is connected and re-connected it's not recognized.
Running "pkill -U $USER pulseaudio" solves this problem in 8/10 cases.
The other 2/10 are full system reboots.
Attached is the dpkg.log with the updates from 2020-03-02 and
2020-03-04. I couldn't determine anything that would point near the/a
problematic package.
I still need to find a way to restart pulseaudio with a higher debug
level to check if anything pops up with pulse.
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
** Attachment added: "dpkg_200305.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+attachment/5334241/+files/dpkg_200305.log
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
I tested all versions since 18.04 up to 20.04, in no live session I
could reproduce this problem. Yet this problem occurs in our
installations. The youngest installation is about three weeks old and
has the same bug.
Is there a way to end pulseaudio and prevent it from auto-restarting, so
I can try and get some debug from "pulseaudio -vvv"? Killing the process
with kill/pkill, or with "pulseaudio --kill" restarts it immediately.
Attached is the output to syslog when dis- and reconnectiong the USB
headset.
** Attachment added: "pulseaudio_syslog"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+attachment/5333028/+files/pulseaudio_syslog
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
Fix Released
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
Got feedback from one of my colleagues that running Ubuntu 18.04.4 with
Kernel 5.3.0-40, "pkill -U $USER pulseaudio" does not resolve the
problem, only a full restart of the system.
Is there anything I can do to provide additional logs? Running a
debugger when plugging in the headset, logfiles with a specific log
level?
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
Fix Released
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
Just tested with Ubuntu 20.04, the problem does not occur in the live
session.
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
Incomplete
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
** Summary changed:
- pulseaudio doesn't new usb headset
+ pulseaudio doesn't detect (new) USB headset
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865499] [NEW] pulseaudio doesn't detect (new) USB headset
Public bug reported:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized, or
the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker and
the "multichannel" microphone are recognized, only one can be used -
either speaker or microphone. When selecting the speaker, the microphone
is switched back to any other device available, them same goes for the
microphone and the speaker - any other speaker is selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a second
headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282) and
it sounds somewhat very familiar, but instead of "env={}" in /usr/share
/ubuntu-drivers-common/detect/sl-modem.py there's "env=env". Removing
"env=env" doesn't resolve the problem.
Do you require additional information?
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "pulseaudio.info"
https://bugs.launchpad.net/bugs/1865499/+attachment/5332737/+files/pulseaudio.info
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
** Attachment added: "lspcik.txt (new)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+attachment/5318841/+files/lspcik.txt -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
Attached are the three log files, and a new crash report (upload now worked with apport-cli): https://errors.ubuntu.com/oops/327a1f18-32cd- 11ea-b1f2-fa163e983629 -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
dmesg.txt (new) ** Attachment added: "dmesg.txt (new)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+attachment/5318840/+files/dmesg.txt -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
** Attachment added: "prevboot.txt (new)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+attachment/5318842/+files/prevboot.txt -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
apport-cli failed as well. This is the crash report from yestermorning: https://errors.ubuntu.com/oops/24bfc517-306a-11ea-a772-fa163ee63de6. -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
I executed "ubuntu-bug /var/crash/crashfile.crash" but can't see a bug ID. On my whoopsie page, no new entry is created. How do I find out which bug ID was assigned to my ubuntu-bug call? -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856846/+attachment/5316949/+files/lspcik.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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856846/+attachment/5316948/+files/dmesg.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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
Attached are the three requested files. -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856846/+attachment/5316951/+files/prevboot.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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856846/+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 1856846] [NEW] GDM3 login loop with X11
Public bug reported: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description:Ubuntu 18.04.3 LTS Release:18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1856846 Title: GDM3 login loop with X11 Status in gdm3 package in Ubuntu: New Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856846/+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
