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 th
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 not
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905010
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905010
Title:
[s
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/190
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905010
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905010
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905010
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905010
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905010
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905010
Title:
[sna
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/190
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905010
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905010
Title:
[sna
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905010
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
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 de
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856846
Title:
Gnome Xorg sessions fail to start with LDAP users (but Way
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 aga
Unfortunately it's not fixed (on laptops not using -proposed) and
somehow broken on my laptop again (using -proposed). I just had to kill
pulseaudio again to get the headphones and microphone to be both
detected (else only the microphone was detected).
We install the laptops using 18.04.3, updatin
Is there any way I can assist in releasing the fixes? If I remember
correctly I saw the updates for a brief moment in -updates and not in
-proposed anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
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.
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 Ubuntu
Bugs, which is subscri
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865499
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 in
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/186
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 tr
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 wit
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) USB headset
To manage not
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) U
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, t
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/185684
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856846
Titl
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 Ubuntu
Bugs, which is subscribed to Ubunt
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856846
Title:
Gno
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856846
Title:
G
Attached are the three requested files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856846
Title:
Gnome Xorg sessions fail to start with LDAP users (but Wayland or
local users work)
To manage
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856846
Title:
I'll add the log asap.
> Could you also give details on what you mean 'GDM loops around three to five
> times'?
Sure. GDM starts, I select my user to log in with, I enter my password, the
screen goes blank for two seconds, and I'm back at the user selection.
The password is not entered incorrec
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) th
51 matches
Mail list logo
