sos report of the jammy host
** Attachment added: "sosreport-ip-172-31-19-168-2024-06-04-gtcbeon.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2068030/+attachment/5785859/+files/sosreport-ip-172-31-19-168-2024-06-04-gtcbeon.tar.xz
--
You received this bug
Public bug reported:
ubuntu-drivers is not returning any driver for g5g instances in AWS,
which use Tesla T4G cards:
# lspci -tv
-[:00]-+-00.0 Amazon.com, Inc. Device 0200
+-01.0 Amazon.com, Inc. Device 8250
+-04.0 Amazon.com, Inc. NVMe EBS Controller
Well, I cannot explain why but my problematic monitor decided to work well even
without forcing hotplug, so now I cannot test the new kernels because I can't
see the problem anymore.
I'll revisit this if it starts misbehaving again.
--
You received this bug notification because you are a
@Dave so I tested this in 4 other monitors and they all worked as
expected without the need for forcing hotplug.
@Juerg you could say it's a regression because it worked on that
specific monitor and now it does not work anymore, but it is now
understood what happend and the reason for that (there
Thank you for the explanation.
So that means that with different monitors I could potentially not need
this vc4.force_hotplug option, right? I will (as time permits) try
plugging this device in all my other monitors to compare, let's see how
it goes (this monitor specifically is a laptop LCD
Ok, adding vc4.force_hotplug=0x01 to the kernel command line _does_ fix
the issue, the screen flickers for a second but comes back with normal
image and stays on.
Also, now I seem to be able to decode edid many times in a row without
it disappearing (appearing empty).
I'm not running the test of
This is the complete boot log, just in case something in it is useful
(taken from the serial console including the firmware initialization
part):
https://pastebin.canonical.com/p/2HMBbBdcFp/
This is the config file used in that boot (which btw is the stock file
from image, unchanged):
Found one more bug report that may be related:
https://github.com/raspberrypi/linux/issues/5195
** Bug watch added: github.com/raspberrypi/linux/issues #5195
https://github.com/raspberrypi/linux/issues/5195
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Ok, running some tests.
First thing is that with fKMS overlay, right on boot (even before the
kernel started) I can see these messages on the serial console:
RPi: BOOTLOADER release VERSION:0b7b6f28 DATE: 2024/04/17 TIME: 13:51:36
BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1713358296
I just found a usb flash key with my last installation (from a daily
image) from a few days ago, and it does not have a line for that
dtoverlay at all (neither fkms nor kms).
This line seems to have appeared on the official release.
--
You received this bug notification because you are a member
Public bug reported:
I just flashed noble arm64+raspi image and booted it in my raspberry pi 4, and
after initial rainbow screen kernel boots with 4 raspberries on the top and
boot text appears as normal. But then, before it finishes booting, the screen
goes blank.
Image is
Public bug reported:
$ pwd
/usr/share/doc/openssl
$ ls -l
total 52
lrwxrwxrwx 1 root root30 mars 31 08:42 changelog.Debian.gz ->
../libssl3/changelog.Debian.gz
lrwxrwxrwx 1 root root23 mars 31 08:42 changelog.gz ->
../libssl3/changelog.gz
lrwxrwxrwx 1 root root20 mars 31 08:42
Weichen,
this was a bug on the snapd package until version 2.61.2:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2057491
snapd is now updated to 2.61.3 and the issue is fixed. It's unrelated to
the changes you made.
I also tried to reproduce it in my environment with a fresh
Still any news yet?
I want to emphasize that two updates to two Ubuntu LTS versions broke the one
of the main features of the preferred container runtime on Ubuntu (over
docker). A patch is ready and tested and after six weeks no further reaction...
Greetings,
André
--
You received this bug
I'm not that invested in the having openssh-server installed but not
running use-case, but in general people do not like their local
configuration beeing overridden on package upgrades in this manner.
I could image people having it installed for the man-pages, or maybe
using other units for it
Public bug reported:
the openssh-server 1:9.6p1-3ubuntu11 postinst contains this code
snippet:
if [ "$action" == configure ]; then
..snip..
if dpkg --compare-versions "$2" lt-nl 1:9.6p1-3ubuntu3~; then
..snip..
if [ -d /run/systemd/system ]; then
# Make sure ssh.service is
Public bug reported:
Recently introduced sshd-socket-generator for socket activation in
openssh 1:9.6p1-3ubuntu3 has a bug when dealing with multiple Port or
ListenAddress entries in the sshd configuration.
If you have multiple Port or ListenAddress and one of them is for port
22, it just skips
Hi @all,
a colleague of mine also experienced the same problem with Ubuntu linux kernel
version 5.15.0-101 (on Ubuntu 22.04). The patch I made
(ignore_enotsup_when_chmod_a_symlink.patch) fixes also this problem.
Greetings,
André
--
You received this bug notification because you are a member
What is the correct PPA to have the newest landscape clients until this
is fixed?
I found ppa:landscape/production which is very outdated, and
ppa:landscape/trunk which does have version 23.10 but it seems odd that
a customer needs to use "trunk" and not "production". Also I was
avoiding pointing
** Package changed: crun (Ubuntu) => linux-meta-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052961
Title:
Error: OCI runtime error: crun: chmod : Operation not supported
To
Hi @all,
I was also unable to run systemd with kernel 6.5.0-21-generic, got the exactly
the same problem.
I backported
https://github.com/containers/crun/commit/be16ee75ff8574698250352302e9d5496d888d69
as a quilt patch for the ubuntu recent version of crun 0.17+dfsg-1.1 (see
attachment). After
The problem is that a swapfile in btrfs cannot have CoW activated on the
file, and cannot be compressed. Also, you should not leave the file in
the root filesystem (even if it would work with the above settings)
because it will make snapshots of /@ messy.
If you manually do this, it will work:
-
Public bug reported:
If you try to import a custom image in maas cli it fails with a cryptic error
which turns out to be because of a non-existing architecture.
Upon further investigation, it seems that if you delete all images of a
specific architecture the architecture itself disappears and
I've also retested your fix. It works like a charm. Thank you very much.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968335
Title:
apparmor profile needs extension
To manage notifications about
Please consider backporting for Focal (20.04) at least. The backport is
trivial and applies cleanly as-is except for patch offsets.
Might be wise to test some other combinations though. For example hosts
without this commit, running nspawn containers with it.
--
You received this bug
Just tested, and can confirm backporting
e8cf09b2a2ad0d48e5493050d54251d5f512d9b6 to focal's systemd fixes the
segfaults when using machinectl shell on a Jammy host trying to start a
shell in a Focal nspawn container.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Hi team,
I've tried to create a socket activated systemd service for supplying a
software tpm for qemu. As it didn't worked I recognized that the swtpm package
ships an apparmor profile. To make it work i've to add a read/write/lock
permission for the tpm's nvram folder
I noticed my usb audio started crackling on the last few days. It does
not happen on internal audio, just on my Xenyx 302 USB external mixer. I
followed the suggestion of reverting to old kernel above and it seems to
have fixed the issue.
5.13.0-37 has issues, 5.13.0-35 is good.
Please let me
Changing to confirmed because it affects at least 3 people.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966432
Title:
audio crackling on usb sound card
To manage notifications about this bug go
Public bug reported:
Hi,
I'm trying to rebuild a traditional server installer, therefore I've to build
Debian-Installer udeb Packages. But this does not work with debhelper
13.6ubuntu1 on the actual ubuntu 22.04 prerelease. I found the root cause: It's
ubuntu specific patch on debhelper
Public bug reported:
Black Screen !!!not during Boot!!! !!!during Work!!!
1)
New lap top and new installation of Ubuntu 20.04.3 lts
2)
apt-cache policy pkgname is not working; Pkgconf? > Version table: 1.6.3-5 500
Hardware:
Dell XPS17 with Intel Core i9
GPU Nvidia GeForce RTX 3060 incl Driver
Confirmed, everything working as it should. LB is online/active, all resources
working well (health checsks, backends, etc.). Even adding a FIP and accessing
from "outside".
I'm closing as invalid, and keeping the other bug.
** Changed in: octavia (Ubuntu)
Status: Confirmed => Invalid
I created a new bug for FCE -->
https://bugs.launchpad.net/cpe-foundation/+bug/1950678
I could not just add it here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950350
Title:
octavia LBs
Ok, I was taking a deeper look at corey's output (where it shows LB is active)
(comment #8) and wanted to try that "ovn" driver that appears on his output
(not directly related to this problem, but anyway).
Then I saw the documentation saying that if you deploy octavia with OVN
you should get
I removed all configs (flavor, flavorprofile, availabilityzone,
availabilityzoneprofile) and just created a very simple loadbalancer passing
only name and network options.
It still get ACTIVE/OFFLINE.
ubuntu@app1maas001p:~/2021-09-20-OP-212891-xxx-Prod1$ openstack loadbalancer
list
I'm taking a step back and trying to just create a simple loadbalancer
without any resources and get that ONLINE, like you can see here (from
coreycb):
https://paste.ubuntu.com/p/NRdsvPrRhB/
Instead, I get this:
https://pastebin.canonical.com/p/FGcwHkgZ27/
The amphora image in these tests was
https://pastebin.canonical.com/p/rW8b88MRVj/
Also found these errors in /var/log/octavia/octavia-worker.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950350
Title:
octavia LBs always offline
https://pastebin.canonical.com/p/dnq9sBZMKn/
Found SQL error in /var/log/octavia/octavia-health-manager.log about
health monitor. I have very similar messagens on the 3 octavia units.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have no errors when installing octavia, nothing unusual on the juju logs.
I'm searching for specific backend health logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950350
Title:
octavia LBs
https://pastebin.canonical.com/p/fBwxNVPVB7/
This is the whole loadbalancer creation log. You can see all backends
are "offline" at the end (and they stay offline).
https://pastebin.canonical.com/p/yZVCb2Py63/
This is all the security groups on the system, including the ones
created byu
I have tried to add ALL possible roles related to octavia to the admin user and
it did not improve the situation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950350
Title:
octavia LBs always
Public bug reported:
After switching from Wallaby to Xena, the same procedure to create a simple
loadbalancer is no longer working (both from dashboard and from CLI). All
backends appear as offline, as if the monitor tests were failing, although the
service is accessible.
** Affects: octavia
Subscribed field-critical.
I'll add more information as soon as possible, but I'm available for
debugging if someone can work on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950350
Title:
I changed the tag for "verification-needed-focal" to "verification-done-
focal", but I would like to add that the version of the kernel listed on
the "focal" fix above is 5.8, when in fact the GA kernel for focal is
5.4.
Kernel 5.8 has been an HWE kernel for focal in the past but even then
it's
I can confirm that this is fixed for focal GA kernel. Kernel 5.4.0-89
still have the problem and kernel 5.4.0-90 is fixed, I can see all nics
on the card now.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are
Sure! I cannot redeploy right now because I'm using the cloud to chase another
bug, bug will do asap and report back.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945707
Title:
Just a comment on wallaby-proposed packages, I installed those on all
ovn-related units and don't see errors about RBAC anymore, and I also didn't
notice any other collateral effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just upgrading the packages (from focal-wallaby-proposed) did not help.
I upgraded on all ovn-chassis (even the octavia ones), all ovn-central,
all ovn-chassis-gateway. I also deleted the LB and recreated completely.
On a separate note, when I try to run "ovn-sbctl find connection" the
command
Ok, I'll try to update from proposed and test. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917475
Title:
RBAC Permissions too strict for Port_Binding table
To manage notifications
I seem to be having this problem on a focal / wallaby deployment, although I
don't have that exact message (about prohibit update of port_binding), I only
have:
root@srv2dell001p:/var/log/ovn# grep -i perm ovn-controller.log
Walter: No, it has not been implemented.
https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/51 is still open.
** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/-/issues #51
https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/51
--
You received this bug notification because you are a member
Ok, I should have waited for the firmware upgrade before posting this.
They seemed to be pretty outdated, went from FW v10.2.377.29 to
v11.4.1186.4
And... drum roll. it worked. Fixed the problem.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You
Just for clarification:
There are 2 DHCP servers on this segment (one in HA, actually). Both
respond, and I can see both Offers in the bridge. One coming straight
from the host and another one form a different host via the uplink.
Neither of them reach the vm (which should receive both and choose
I'm also seeing a lot of "[263380.267602] br-bond0: received packet on bond0
with own address as source address (addr:4a:e1:8f:bc:32:3d, vlan:0)" in dmesg
when I add the ip manually (and it works -- but gives me these messages).
I don't think how a loop could be in play here, with only 1 uplink
I tested setting ageing to 0 (suggested at some internet forums):
brctl setageing br-bond0 0
No improvement.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
Title:
DHCP Offer not traversing
I tried the exact same things on different environments and it always works. It
seems to be something related to this hardware, because it happens exactly the
same on 3 machines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530577/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530576/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530575/+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/1946028
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530574/+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/1946028
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530573/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530572/+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/1946028
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530571/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530570/+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/1946028
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530569/+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/1946028
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530567/+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/1946028
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530568/+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/1946028
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530566/+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/1946028
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530565/+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/1946028
Title:
apport information
** Tags added: apport-collected focal uec-images
** Description changed:
I'm facing a problem in a customer where a VM plugged to a bridge will not
get DHCP responses from dhcp server running on the host or externally (the
bridge has level 2 external uplink).
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530564/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is the netplan config:
network:
ethernets:
eno1: {}
enp22s0f1: {}
bonds:
bond0:
# vlan 3801 - OAM is native (no tag)
interfaces:
- eno1
- enp22s0f1
parameters:
primary: eno1
mode: active-backup
mii-monitor-interval: 1s
This is the bridge info:
ubuntu@app2maas001p:~$ brctl show br-bond0
bridge name bridge id STP enabled interfaces
br-bond08000.723488506c2c no bond0
tap864c7e54
ubuntu@app2maas001p:~$
Iptables is empty with all ACCEPT policy.
ebtables is empty with all ACCEPT policy.
ufw is inactive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
Title:
DHCP Offer not traversing linux
Public bug reported:
I'm facing a problem in a customer where a VM plugged to a bridge will not get
DHCP responses from dhcp server running on the host or externally (the bridge
has level 2 external uplink).
Relevant information:
- focal with latest GA kernel (5.4.0-88)
- tested with HWE
I'm seeing this in focal kernel 5.4.0-88. Is this expected? Do I have to
switch to the hwe kernel pointed above to fix this?
The laptop has been stable for a long time and then suddenly started
having this exact symptom a few days ago. I'm wondering if this was
introduced in latest ga kernels for
This seems to be the upstream bug:
https://bugzilla.kernel.org/show_bug.cgi?id=214297
** Bug watch added: Linux Kernel Bug Tracker #214297
https://bugzilla.kernel.org/show_bug.cgi?id=214297
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Works with focal kernel 5.4.0-80
Broken with focal kernel 5.4.0-88
On a Dell R720 with the BCM57800 based 1/10 Gigabit Integrated Network
cards Kernel 5.11.22-3 causes half of the network interfaces to
disappear specifically the 1gb ports. Commands like "ip link show" and
Public bug reported:
Hello
Got the error below when running a apt update command:
fandre@ubuntu-18-04:~$ sudo apt update
[sudo] password for fandre:
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic InRelease
Get:3
Public bug reported:
Description:Ubuntu 20.10
Release:20.10
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubuntu-release-upgrader-core 1:20.10.16
ProcVersionSignature: Ubuntu 5.8.0-63.71-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.7
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).
If you can
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).
If you can
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
Bluetooth unavailable after updates - Reading Intel version
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).
If you can
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).
If you can
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
(resources are unfortunately quite limited so not every ticket can get handled).
If you can still reproduce the situation described in this
** Bug watch added: gitlab.gnome.org/GNOME/gthumb/-/issues #101
https://gitlab.gnome.org/GNOME/gthumb/-/issues/101
** Also affects: gthumb via
https://gitlab.gnome.org/GNOME/gthumb/-/issues/101
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
For any poor saps that encounter this in the future in a similar
situation, replacing the graphics driver with 'virtio' in the KVM/qemu
config fixes this:
Instead of the default 'cirrus' or whatever. Found this in my age-old
notes from the last time I encountered this problem
I get this error which the internet suggests means a problem getting a
core dump. Upping the limits didn't in apport didn't seem to help. I
attached the file in /var/crash
$ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash
*** Error: Problem in gnome-shell
Sorry, the program "gnome-shell"
I'm seeing this crash on a brand new Ubuntu 18.04 install running on KVM
(the host itself is on 16.04). When I connect via KVM's VNC and try to
open settings app, I get a 100% crash. It's weird because I haven't
installed any additional software.
Mar 18 22:42:11 riv18
I've attached the full logs I see. Can anyone tell me where to look for
more details?
** Attachment added: "ubuntu-logs"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+attachment/5478029/+files/ubuntu-logs
--
You received this bug notification because you are a member
Hi!
Are you sure this is not a hardware issue?
The reason I believe it is a hardware issue is because I observed my
system "drop monitors" on the docking station also under Windows 10 and
even while in the UEFI. Lenovo replaced both the motherboard and the
docking station (and I updated firmware
With kernel version 5.6.0-1048-oem, the stack trace looks different, but
the problem is still present.
[ 4881.023648] [ cut here ]
[ 4881.023782] WARNING: CPU: 1 PID: 1113 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:1555
Please provide a backtrace of the crash - see
https://wiki.ubuntu.com/DebuggingProgramCrash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910267
Title:
Evolution crash very often doing nothing
Public bug reported:
During Installation
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion:
bugzilla.gnome.org is being shut down in favor of a GitLab instance.
We are closing all old bug reports and feature requests in GNOME Bugzilla which
have not seen updates for a long time.
If you still use NetworkManager and if you still see this bug / want
this feature in a recent and supported
bugzilla.gnome.org is being shut down in favor of a GitLab instance.
We are closing all old bug reports and feature requests in GNOME Bugzilla which
have not seen updates for a long time.
If you still use NetworkManager and if you still see this bug / want
this feature in a recent and supported
bugzilla.gnome.org is being shut down in favor of a GitLab instance.
We are closing all old bug reports and feature requests in GNOME Bugzilla which
have not seen updates for a long time.
If you still use NetworkManager and if you still see this bug / want
this feature in a recent and supported
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing
all old bug reports in Bugzilla which have not seen updates for many
years.
If you can still reproduce this issue in a currently supported version
of GNOME (currently that would be 3.38), then please feel free to report
it
Since I just had the system "drop monitors" while in the UEFI with no OS
booted, this might not be an OS issue at all.
It can't be a docking / USB-C issue either, since the system sometimes
can't even switch to internal display and it also crashes with an
external monitor attached directly via
1 - 100 of 1735 matches
Mail list logo
