[Bug 1982969] Re: Missing binary package for octavia prometheus-proxy
I have taken a look at this with the customer and indeed it seems a matter of adding a file to the deb package (file which is already in the sources, just being missed while packaging). Half of the functionality is there (the proxy itself) but the systemd-unit that starts the proxy is missing. Adding that file manually to the file-system fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1982969 Title: Missing binary package for octavia prometheus-proxy To manage notifications about this bug go to: https://bugs.launchpad.net/snap-octavia-diskimage-retrofit/+bug/1982969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012309] Re: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04
Seems like the application *is* started. I went to a tty shell and took a list of processes running while the gdm was showing and saw that the application was there, as a child to gdm. But it does not show on the screen, probably something related to wayland? Still investigating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012309 Title: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012309] Re: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04
Correction, opening an app AFTER the user logged in is working in 24.04, it was a mistake in my tests. Bu I still need to open an application in the gdm session itself, which still seems to be broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012309 Title: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012309] Re: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04
I'm seeing the same behavior in 24.04. AFAIK the /usr/share/gdm/greeter/autostart/ is for apps to be started in the GDM screen itself while the /usr/share/gdm/autostart/LoginWindow/ is for apps to be started after the user logged in, which are different things. Both seem broken to me right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012309 Title: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068030] Re: No drivers detected for TU104GL [T4G] card
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068030 Title: No drivers detected for TU104GL [T4G] card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2068030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068030] [NEW] No drivers detected for TU104GL [T4G] card
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 +-05.0 Amazon.com, Inc. Elastic Network Adapter (ENA) \-1f.0 NVIDIA Corporation TU104GL [T4G] # ubuntu-drivers --gpgpu list This is gpgpu mode # uname -a Linux ip-172-31-16-212 6.8.0-1008-aws #8-Ubuntu SMP Sat Apr 20 02:43:14 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 24.04 LTS Release:24.04 Codename: noble Processor: Handle 0x0004, DMI type 4, 42 bytes Processor Information Socket Designation: CPU00 Type: Central Processor Family: ARMv8 Manufacturer: AWS ID: C1 D0 3F 41 00 00 00 00 Signature: Implementor 0x41, Variant 0x3, Architecture 15, Part 0xd0c, Revision 1 Version: AWS Graviton2 I tried Noble and Jammy and both have the same behavior. Manually installing the drivers works as expected (below is the output in Jammy, as Noble is hitting https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-550-server/+bug/2062380 and freezes on module loading) $ sudo nvidia-smi Tue Jun 4 14:18:15 2024 +---+ | NVIDIA-SMI 535.161.08 Driver Version: 535.161.08 CUDA Version: 12.2 | |-+--+--+ | GPU Name Persistence-M | Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=+==+==| | 0 NVIDIA T4G Off | :00:1F.0 Off | 0 | | N/A 36CP0 27W / 70W | 2MiB / 15360MiB | 4% Default | | | | N/A | +-+--+--+ +---+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |===| | No running processes found | +---+ ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068030 Title: No drivers detected for TU104GL [T4G] card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2068030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
@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 was a switch from fkms to kms right before official release and all my other tests were with daily builds which were not using kms yet). But since it still works ok with all my other monitors I'm not sure how much it is a regression or how much it is just a fault of my specific hardware. Anyway, I'll test both kernels and let you know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
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 using a lcd controller from ebay -- the others are all lg/samsung/dell ones, should behave better). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
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 forcing an edid.bin file because now there seems to be no point in doing it, let me know if you need this or any other test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
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): https://pastebin.canonical.com/p/ySzZhbwPf2/ Note that the screen goes blank at the very end of that log, a few lines before the login prompt (cannot say exactly where, seems to be around the EXT4-fs (sda2): re-mounted message. At the same time, this logs seems to be incomplete compared from what I can see on the HDMI output when it works (in that case, with fKMS), I can see many more lines between those last "rcu:" lines and the prompt which I cannot see on the serial. Edit: I just realised the difference is that I only see kernel messages on serial while I see kernel messages + systemd service messages on hdmi. No real problem here. Unpluggin power to the monitor after it went dark and pluggin it back does not help (this was suggested in one of the github issues). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
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 serial a0940f46 boardrev b03111 stc (lots of lines removed) Boot mode: USB-MSD (04) order e HDMI0 edid block 0 offset 0 000049f7 011a01038ad7a5a2594a9624 145054afce0081c00101010101010101 0101010101017f2156aa51001e30468f 33003f43211ea91a00a050001630 302037002056001a00fd0032 4c1e501a20202020202000fc 004141410a20202020202020200a016f HDMI0 edid block 1 offset 128 020323744f109f140504131216111503 0702060123090f03830166030c00 100080011d00bc52d01e20b8285540c4 8e211e011d80d0721c1620102c25 80c48e219e8c0ad08a20e02d1010 3e9600138e21188c0ad090204031 200c405500138e211800 009d HDMI0: best-mode 1 (limit 1) 1280x720 60 Hz CEA modes fe007f80 extensions 1 USB2[1] 400202e1 connected If I switch to the KMS overlay, the message is exactly the same, so it means the EDID is accessible from the monitor in either case. I compared both outputs and they are the same. But with KMS, as expected, the monitor went blank again by the end of the boot messages. Another interesting thing is that I *could* dump edid even with the KMS overlay right after boot, once. When I tried again, it did not work anymore, saying it was empty: ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid edid-decode (hex): 00 ff ff ff ff ff ff 00 49 f7 00 00 00 00 00 00 01 1a 01 03 80 00 00 00 0a d7 a5 a2 59 4a 96 24 14 50 54 af ce 00 81 c0 01 01 01 01 01 01 01 01 01 01 01 01 01 01 7f 21 56 aa 51 00 1e 30 46 8f 33 00 3f 43 21 00 00 1e a9 1a 00 a0 50 00 16 30 30 20 37 00 20 56 00 00 00 1a 00 00 00 fd 00 32 4c 1e 50 10 00 0a 20 20 20 20 20 20 00 00 00 fc 00 41 41 41 0a 20 20 20 20 20 20 20 20 0a 01 6f 02 03 23 74 4f 10 9f 14 05 04 13 12 16 11 15 03 07 02 06 01 23 09 0f 03 83 01 00 00 66 03 0c 00 10 00 80 01 1d 00 bc 52 d0 1e 20 b8 28 55 40 c4 8e 21 00 00 1e 01 1d 80 d0 72 1c 16 20 10 2c 25 80 c4 8e 21 00 00 9e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 13 8e 21 00 00 18 8c 0a d0 90 20 40 31 20 0c 40 55 00 13 8e 21 00 00 18 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9d Block 0, Base EDID: EDID Structure Version & Revision: 1.3 Vendor & Product Identification: Manufacturer: ROW Model: 0 Made in: week 1 of 2016 Basic Display Parameters & Features: Digital display Image size is variable Gamma: 1.00 RGB color display First detailed timing is the preferred timing Color Characteristics: Red : 0.6357, 0.3486 Green: 0.2900, 0.5888 Blue : 0.1425, 0.0800 White: 0.3134, 0.3291 Established Timings I & II: IBM : 720x40070.081663 Hz 9:5 31.467 kHz 28.32 MHz DMT 0x04: 640x48059.940476 Hz 4:3 31.469 kHz 25.175000 MHz DMT 0x05: 640x48072.808802 Hz 4:3 37.861 kHz 31.50 MHz DMT 0x06: 640x48075.00 Hz 4:3 37.500 kHz 31.50 MHz DMT 0x08: 800x60056.25 Hz 4:3 35.156 kHz 36.00 MHz DMT 0x09: 800x60060.316541 Hz 4:3 37.879 kHz 40.00 MHz DMT 0x0a: 800x60072.187572 Hz 4:3 48.077 kHz 50.00 MHz DMT 0x0b: 800x60075.00 Hz 4:3 46.875 kHz 49.50 MHz DMT 0x10: 1024x76860.003840 Hz 4:3 48.363 kHz 65.00 MHz DMT 0x11: 1024x76870.069359 Hz 4:3 56.476 kHz 75.00 MHz DMT 0x12: 1024x76875.028582 Hz 4:3 60.023 kHz 78.75 MHz Standard Timings: DMT 0x55: 1280x72060.00 Hz 16:9 45.000 kHz 74.25 MHz Detailed Timing Descriptors: DTD 1: 1366x76859.964364 Hz 683:384 47.852 kHz 85.75 MHz (575 mm x 323 mm) Hfront 70 Hsync 143 Hback 213 Hpol P Vfront3 Vsync 3 Vback 24 Vpol P DTD 2: 1280x76859.994726 Hz 5:3 47.396 kHz 68.25 MHz (32 mm x 86 mm) Hfront 48 Hsync 32 Hback 80 Hpol P Vfront3 Vsync 7 Vback 12 Vpol N Display Range Limits: Monitor ranges (GTF): 50-76 Hz V, 30-80 kHz H, max dotclock 160 MHz Display Product Name: 'AAA' Extension blocks: 1 Checksum: 0x6f Block 1, CTA-861 Extension Block: Revision: 3 Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 Native detailed modes: 4 Video Data Block: VIC 16: 1920x1080 60.00 Hz 16:9 67.500 kHz148.50 MHz VIC 31: 1920x1080 50.00 Hz 16:9 56.250 kHz148.50 MHz (native) VIC 20: 1920x1080i 50.00 Hz 16:9 28.125 kHz 74.25 MHz VIC 5: 1920x1080i 60.00 Hz 16:9 33.750 kHz 74.25
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] [NEW] Blank screen after boot in raspberry pi 4
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 ubuntu-24.04-preinstalled-server-arm64+raspi.img.xz downloaded at Apr/30. ubuntu@ubuntu:~$ uname -a Linux ubuntu 6.8.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 02:29:55 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux I know the system booted because I can access it over the network and I even plugged a usb-serial adapter in the uart GPIOs and from there I can see the boot does progress to completion and offers me a prompt where I can use the system normally. But the HDMI screen stays blank. The funny thing is that I have been trying daily builds for quite some time now and they used to work well, this is the first one that does this (the official release). After testing some config options I found that if I change "dtoverlay=vc4-kms-v3d" for "dtoverlay=vc4-fkms-v3d" in config.txt then it boots ok and the screen stays on (note the change from kms to fkms). I also tried appending ",cma-128" to that line (it is present on other lines -- like for pi3 and pi0 -- but not on this one), it does not help. I don't think the issue is with my monitor since it works well for a long time. Also I checked EDIDs, they are detected when using fkms but they are blank when using kms: With KMS: ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid EDID of '/sys/class/drm/card0-HDMI-A-1/edid' was empty. With fKMS: ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid edid-decode (hex): 00 ff ff ff ff ff ff 00 49 f7 00 00 00 00 00 00 01 1a 01 03 80 00 00 00 0a d7 a5 a2 59 4a 96 24 .. (supressed) I do not use a graphical environment on this unit so I don't know the consequences of this change (to me it just fixes the issue, but I guess it was there for a reason). Let me know if you need any other information from the environment. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063898] [NEW] broken doc symlinks after t64 transition in noble
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 copyright -> ../libssl3/copyright libssl3 doenst exist anymore, it is now libssl3t64 $ apt-cache policy openssl libssl3t64 openssl: Installed: 3.0.13-0ubuntu3 Candidate: 3.0.13-0ubuntu3 Version table: *** 3.0.13-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status libssl3t64: Installed: 3.0.13-0ubuntu3 Candidate: 3.0.13-0ubuntu3 Version table: *** 3.0.13-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063898 Title: broken doc symlinks after t64 transition in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2063898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061068] Re: debsums check failed
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 installation and the issue didn't manifest, so I can confirm it's fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061068 Title: debsums check failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052961] Re: Error: OCI runtime error: crun: chmod : Operation not supported
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crun/+bug/2052961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059874] Re: on upgrade sshd-socket-generator conversion does not respect administrator intent
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 (per VRF instances or something), having the main service and socket units disabled, but I doubt that happens that much in practice. For me the biggest problem was the socket unit beeing re-enabled when I had it disabled it but still running sshd.service (ie without socket activation) - now you're unexpectidly switched back to using socket activation - something I explicitly opted out of. I could also see this causing problems if you have the socket unit masked (dont see why you would want that however) but the the service is enabled, now you are without sshd. Actually I think the postinst would also fail in that case, as systemctl enable fails enabling masked units. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059874 Title: on upgrade sshd-socket-generator conversion does not respect administrator intent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059874] [NEW] on upgrade sshd-socket-generator conversion does not respect administrator intent
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 disabled. systemctl unmask ssh.service systemctl disable --now ssh.service > /dev/null 2>&1 # sshd-socket-generator is invoked on daemon-reload. systemctl daemon-reload systemctl enable ssh.socket fi fi fi This does not respect existing service and socket unit configuration, it effectively re-enables a disabled ssh.service (and even a masked one), and a manually disabled socket unit. I strongly suspect it does not respect systemd presets either. This is unexpected behaviour. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059874 Title: on upgrade sshd-socket-generator conversion does not respect administrator intent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059872] [NEW] Unable to listen on port 22 if multiple Port= present in sshd configuration
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 it. To show it clearly, here is an example: Port 22 Port 1024 It generates: ListenStream= ListenStream=1024 Now nothing is listening to port 22, hence breaking existing configurations. This was tested on 1:9.6p1-3ubuntu11. The intention seems to be to not generate the drop-in if only port 22 is in use, but it does not account for the case of multiple Port or ListenAddress where one of them is for port 22. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059872 Title: Unable to listen on port 22 if multiple Port= present in sshd configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052961] Re: Error: OCI runtime error: crun: chmod : Operation not supported
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crun/+bug/2052961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2006402] Re: Update focal, jammy to landscape-client 23.02
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 the customer a the server repo (for example ppa:landscape/self-hosted-*) because it can be confusing/dangerous for a customer to be able to install the server in a workstation by mistake. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2006402 Title: Update focal, jammy to landscape-client 23.02 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2006402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052961] Re: Error: OCI runtime error: crun: chmod : Operation not supported
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2052961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052961] Re: Error: OCI runtime error: crun: chmod : Operation not supported
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 applying the patch, systemd works again as expected. Grettings, André ** Patch added: "ignore_enotsup_when_chmod_a_symlink.patch" https://bugs.launchpad.net/ubuntu/+source/crun/+bug/2052961/+attachment/5749829/+files/ignore_enotsup_when_chmod_a_symlink.patch -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crun/+bug/2052961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Ubuntu-BR] [email] via terminal - usando o mutt
Olá Fábio bom dia. Em qua, 19 de out de 2022 09:24, Fabio Bairros escreveu: > Saudações > > Estou usando o ubuntu mini e gostaria de enviar e-mails usando o mutt (por > exemplo) e enviar arquivos anexados. Fiz a instalação do mutt, mas os > e-mails não são enviados, ficam na caixa indicando impossibilidade de > entrega. Existe alguma outra configuração necessária ? > O mutt é só o front end. Você ainda precisa instalar quem realmente faz as coisas, por exemplo, sendmail. Veja a documentação. Eu uso o mutt principalmente em scripts e funciona muito bem, inclusive com o gmail. Mas tens que configurar a senha de aplicativo no gmail e o mutt para usar https e essa senha. Abraços. André Cavalcante Manaus, AM. > > > > > att, > Fabio Bairros > -- > Mais sobre o Ubuntu em português: http://www.ubuntu-br.org/comece > > Lista de discussão Ubuntu Brasil > Histórico, descadastramento e outras opções: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-br > -- Mais sobre o Ubuntu em português: http://www.ubuntu-br.org/comece Lista de discussão Ubuntu Brasil Histórico, descadastramento e outras opções: https://lists.ubuntu.com/mailman/listinfo/ubuntu-br
[Bug 1818811] Re: The swapfile on the Btrfs file system is not activated
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: - create a separate subvolume just for swap - mount it somewhere like /swap (also add to fstab) - create an empty file (/swap/swapfile) - set non-compress and no-CoW on the file - grow the file to the desired size - mkswap on the file - add swap file to fstab now you can swapon -a and it will work. The installer does not do that, it just creates a /swapfile as it would do on any other filesystem and then on reboot it will not start. Amano instructions above will work, but I would advise to also create the subvolume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818811 Title: The swapfile on the Btrfs file system is not activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969510] [NEW] MaaS deletes image architectures if you delete all images of that architecture
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 then you cannot add a custom image, which will fail. Workaround is to go back to the images section in the GUI, select some ubuntu image of that architecture, wait for it to download and then re- try adding the custom image which will then work. This is very non-intuitive for end users, and also it's possible for an airgapped environment to erase all images and then get into a situation where they cannot recover. My understanding is that this is a known behavior, which makes this is bug report a feature-request to 'fix' this to work in a more intuitive way. ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969510 Title: MaaS deletes image architectures if you delete all images of that architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1969510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968335] Re: apparmor profile needs extension
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/swtpm/+bug/1968335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959475] Re: "machinectl shell" connections immediately terminated
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959475 Title: "machinectl shell" connections immediately terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959475] Re: "machinectl shell" connections immediately terminated
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959475 Title: "machinectl shell" connections immediately terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968335] [NEW] apparmor profile needs extension
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 and a read/write permission for the tpm's unix socket used for the connection with qemu. Since there is no default location for the tpm nvram (correct?) I suggest using "/var/lib/swtpm" which follows the /var/lib/ convention. Since there is no default location for the tpm unix socket I suggest using "/run/swtpm/sock" which follows the systemd.socket unit conventions A patch which adds the settings is attached to this message. Greetings, André ** Affects: swtpm (Ubuntu) Importance: Undecided Status: New ** Patch added: "add_socket_and_nvram.diff" https://bugs.launchpad.net/bugs/1968335/+attachment/5578260/+files/add_socket_and_nvram.diff -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/swtpm/+bug/1968335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966432] Re: audio crackling on usb sound card
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 know of any other information you may need to help find the issue. ** 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/1966432 Title: audio crackling on usb sound card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966432] Re: audio crackling on usb sound card
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 to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965984] [NEW] Cannot build udeb with debhelper 13.6ubuntu1
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 described in debian changelog as "Imply
'' profile if not set on package type udeb". I reverted that patch and
now the build of udebs works again.
Greetings,
André
##
Reverting the buggy ubuntu specific patch
##
--- Dh_Lib.pm.orig 2022-03-22 21:27:31.984788688 +0100
+++ Dh_Lib.pm 2022-03-22 21:27:51.352850840 +0100
@@ -1974,9 +1974,6 @@
}
$package_types{$package} =
_strip_spaces($field_values{'package-type'} // 'deb');
-if ($package_types{$package} eq 'udeb' and
!defined($build_profiles)) {
- $build_profiles = '';
-}
$package_arches{$package} = $arch;
$package_multiarches{$package} =
_strip_spaces($field_values{'multi-arch'} // '');
$package_sections{$package} =
_strip_spaces($field_values{'section'} // $source_section);;
#
Howto reproduce the bug:
#
$wget
http://deb.debian.org/debian/pool/main/p/partman-auto-raid/partman-auto-raid_47.dsc
$wget
http://deb.debian.org/debian/pool/main/p/partman-auto-raid/partman-auto-raid_47.tar.xz
$dpkg-source -x partman-auto-raid_47.dsc
$cd partman-auto-raid-47/
$dpkg-buildpackage -us -uc -A
dpkg-buildpackage: info: source package partman-auto-raid
dpkg-buildpackage: info: source version 47
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Holger Wansing
dpkg-source --before-build .
fakeroot debian/rules clean
dh clean --with d-i
dh: warning: No packages to build. Possible architecture mismatch: amd64, want:
all
debian/rules build-indep
dh build-indep --with d-i
dh: warning: No packages to build. Possible architecture mismatch: amd64, want:
all
fakeroot debian/rules binary-indep
dh binary-indep --with d-i
dh: warning: No packages to build. Possible architecture mismatch: amd64, want:
all
dpkg-genbuildinfo --build=all -O../partman-auto-raid_47_all.buildinfo
dpkg-genbuildinfo: error: binary build with no binary artifacts found;
.buildinfo is meaningless
dpkg-buildpackage: error: dpkg-genbuildinfo --build=all
-O../partman-auto-raid_47_all.buildinfo subprocess returned exit status 255
After applying my patch, i.e. reverting the ubuntu specific patch
###
$wget
http://deb.debian.org/debian/pool/main/p/partman-auto-raid/partman-auto-raid_47.dsc
$wget
http://deb.debian.org/debian/pool/main/p/partman-auto-raid/partman-auto-raid_47.tar.xz
$dpkg-source -x partman-auto-raid_47.dsc
$cd partman-auto-raid-47/
$dpkg-buildpackage -us -uc -A
dpkg-buildpackage: info: source package partman-auto-raid
dpkg-buildpackage: info: source version 47
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Holger Wansing
dpkg-source --before-build .
fakeroot debian/rules clean
dh clean --with d-i
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_di_kernel_gencontrol
dh_clean
dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
debian/rules build-indep
dh build-indep --with d-i
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_di_kernel_gencontrol -i
dh_update_autotools_config -i
fakeroot debian/rules binary-indep
dh binary-indep --with d-i
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_testroot -i
dh_prep -i
dh_auto_install --destdir=debian/partman-auto-raid/ -i
dh_auto_install: warning: Compatibility levels before 10 are deprecated (level
9 in use)
dh_install -i
dh_install: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
dh_di_kernel_install -i
dh_di_numbers -i
dh_di_numbers: warning: Compatibility levels before 10 are deprecated (level 9
in use)
dh_installdocs -i
dh_installdocs: warning: Compatibility levels before 10 are deprecated (level 9
in use)
dh_installchangelogs -i
dh_installdebconf -i
dh_perl -i
dh_link -i
dh_strip_nondeterminism -i
dh_compress -i
dh_compress: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
dh_fixperms -i
dh_missing -i
dh_missing: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
dh_installdeb -i
dh_gencontrol -i
dh_md5sums -i
dh_builddeb -i
dpkg-deb: building package 'partman-auto-raid' in
'debian/.debhelper/scratch-space/build-partman-auto-raid/partman-auto-raid_47_all.deb'.
Renaming partman-auto-raid_47_all.deb to partman-auto-raid_47_all.udeb
[Bug 1960505] [NEW] Black Screen during work Nvidia GeForce RTX 3060
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 installed. description: From Time to Time I end up in a black screen during my work. it happens during Writing, using the mouse No specific running Software. Again: It happens during my Work! it is not the Screen safer. It is maybe related to the screen safer. The screen safer usually don't start during work. then I can not log in again. When I close the Laptop and open it again, usually the Login Screens pop up again. If I wait eg. one Hour and I move the mouse, the Login Screen pop up again. I did not fond something in the syslog. Tail -f syslog will not work; > black screen I can not open a other TTY. any advice where to find some detailed Error messages in log files? Tryed to find something in the Internet > nothing. 3) it should not happen. 4) see description. Thanks for Support ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960505 Title: Black Screen during work Nvidia GeForce RTX 3060 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1960505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] Re: octavia LBs always offline in Xena
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 -- 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 in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] Re: octavia LBs always offline in Xena
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 always offline in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] Re: octavia LBs always offline in Xena
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 that automatically. You can see in my outputs that I did not have it, even using OVN. On deeper inspection, I noticed I was missing a relation from the example overlay. This relation is not automatically added by the FCE bundle builder, this one: - - octavia:ovsdb-cms - ovn-central:ovsdb-cms I'm not sure if this is new in Xena, or was already needed before (Wallaby? maybe even Ussuri?). When I added it manually, I did get the OVN driver to appear in the list. And to my surprise, my test loadbalancer (the one with octavia driver) went online!!! This makes it seem like this relation is more important than just the OVN driver itself. Can someone confirm what it is for? Anyway, I'm adding FCE to the affected components. -- 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 in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] Re: octavia LBs always offline in Xena
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 +--+--+--+-+-+--+--+ | id | name | project_id | vip_address | provisioning_status | operating_status | provider | +--+--+--+-+-+--+--+ | 0debcdb0-64a6-47b8-847d-ec6610544711 | lb4 | 4d766f4d974c4419bfe0037f51e0b1aa | 172.16.0.57 | ACTIVE | OFFLINE | amphora | +--+--+--+-+-+--+--+ -- 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 in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] Re: octavia LBs always offline in Xena
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 generated by GSS + retrofit. This is some extra info about the flavors configured on my system: https://pastebin.canonical.com/p/PD875kjXw9/ I still get errors in the logs while creating the LB. These are the last 200 lines of each log file in the first unit (other two are very similar). https://pastebin.canonical.com/p/cdSSfRkj43/ This cloud was tottaly redeployed from scratch for this test. The juju-log for the octavia units do not have anything useful (no errors or clues). -- 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 in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] Re: octavia LBs always offline in Xena
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 in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] Re: octavia LBs always offline in Xena
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. https://bugs.launchpad.net/bugs/1950350 Title: octavia LBs always offline in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] Re: octavia LBs always offline in Xena
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 always offline in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] Re: octavia LBs always offline in Xena
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 octavia. -- 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 in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] Re: octavia LBs always offline in Xena
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 offline in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] [NEW] octavia LBs always offline in Xena
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 (Ubuntu) Importance: Undecided Status: New -- 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 in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] Re: octavia LBs always offline in Xena
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: octavia LBs always offline in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
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 already superceed by 5.11 and now 5.13. I think 5.4 is not mentioned here because the change came from upstream and not from a local patch. Anyway, 5.4.0-90 has the fix. -- 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: BCM57800 SRIOV bug causes interfaces to disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
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: BCM57800 SRIOV bug causes interfaces to disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917475] Re: RBAC Permissions too strict for Port_Binding table
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. https://bugs.launchpad.net/bugs/1917475 Title: RBAC Permissions too strict for Port_Binding table To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1917475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917475] Re: RBAC Permissions too strict for Port_Binding table
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 freezes. Strace shows repeatedly:
poll([{fd=3, events=POLLIN}], 1, 4000) = 0 (Timeout)
getrusage(RUSAGE_THREAD, {ru_utime={tv_sec=0, tv_usec=0}, ru_stime={tv_sec=0,
tv_usec=8964}, ...}) = 0
socket(AF_UNIX, SOCK_STREAM, 0) = 5
fcntl(5, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(5, F_SETFL, O_RDWR|O_NONBLOCK)= 0
connect(5, {sa_family=AF_UNIX, sun_path="/var/run/ovn/ovnsb_db.sock"}, 29) = -1
ENOENT (No such file or directory)
close(5)
Any advice is welcome, 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 about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1917475/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917475] Re: RBAC Permissions too strict for Port_Binding table
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 about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1917475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917475] Re: RBAC Permissions too strict for Port_Binding table
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
│2021-10-19T14:03:41.342Z|00076|ovsdb_idl|WARN|transaction
error: {"details":"RBAC rules for client
\"srv2dell001p.oam.prd.infra.sicredi.net\" role \"ovn-controller\" prohibit row
insertion into table \"Encap\".","│
error":"permission error"}
│2021-10-19T14:03:41.342Z|00079|ovsdb_idl|WARN|transaction
error: {"details":"RBAC rules for client
\"srv2dell001p.oam.prd.infra.sicredi.net\" role \"ovn-controller\" prohibit row
insertion into table \"Chassis\"."│
,"error":"permission error"}
│2021-10-19T14:03:41.343Z|00081|ovsdb_idl|WARN|transaction
error: {"details":"RBAC rules for client
\"srv2dell001p.oam.prd.infra.sicredi.net\" role \"ovn-controller\" prohibit row
insertion into table \"Encap\".","│
error":"permission error"}
│2021-10-19T14:03:41.344Z|00083|ovsdb_idl|WARN|transaction
error: {"details":"RBAC rules for client
\"srv2dell001p.oam.prd.infra.sicredi.net\" role \"ovn-controller\" prohibit row
insertion into table \"Chassis\"."│
,"error":"permission error"}
│2021-10-19T14:03:41.345Z|00085|ovsdb_idl|WARN|transaction
error: {"details":"RBAC rules for client
\"srv2dell001p.oam.prd.infra.sicredi.net\" role \"ovn-controller\" prohibit row
insertion into table \"Chassis\"."│
,"error":"permission error"}
I'm trying to apply the workaround but the ovn-sbctl is not connecting
to the ovndb. Working on that.
Meanwhile, is this considered fixed and released in focal + wallaby?
--
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 about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1917475/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951977] Re: Music library and radio station data should be stored separately
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951977 Title: Music library and radio station data should be stored separately To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/951977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Re: DHCP Offer not traversing linux bridge
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 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 bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Re: DHCP Offer not traversing linux bridge
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 one to answer). When the uplink is out, the one from the host gets through. -- 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 bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Re: DHCP Offer not traversing linux bridge
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 port and 1 vm port. The customer says they have STP enable on the rest of the network and a loop outside is very unlikely. I'm ignoring this for now. -- 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 bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Re: DHCP Offer not traversing linux bridge
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 linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Re: DHCP Offer not traversing linux bridge
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. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] acpidump.txt
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] WifiSyslog.txt
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 Title: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] UdevDb.txt
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: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] ProcModules.txt
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 Title: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] ProcInterrupts.txt
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. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] ProcEnviron.txt
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 Title: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] ProcCpuinfoMinimal.txt
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. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] ProcCpuinfo.txt
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 Title: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Lsusb-v.txt
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: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Lsusb.txt
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: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Lsusb-t.txt
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: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Lspci-vt.txt
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 Title: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Lspci.txt
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: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Re: DHCP Offer not traversing linux bridge
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). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net - I'm verifying if there is firmware updates available but I doubt it. No - extra features (like FCoE, partitioning, etc.) are enabled on the card. - It's a single dual-port mezanine card. + I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq + crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.20 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-09-21 (13 days ago) + InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: IBM BladeCenter HS23 -[7875AC1]- + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 mgag200drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro + ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-88-generic N/A + linux-backports-modules-5.4.0-88-generic N/A + linux-firmware1.187.17 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.4.0-88-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lxd plugdev sudo + _MarkForUpload: True + dmi.bios.date: 05/14/2014 + dmi.bios.vendor: IBM + dmi.bios.version: -[TKE140YUS-1.60]- + dmi.board.name: 00AE761 + dmi.board.vendor: IBM + dmi.chassis.asset.tag: none + dmi.chassis.type: 28 + dmi.chassis.vendor: IBM + dmi.chassis.version: none + dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: + dmi.product.family: System X + dmi.product.name: BladeCenter HS23 -[7875AC1]- + dmi.product.version: 07 + dmi.sys.vendor: IBM ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530563/+files/CRDA.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: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] CurrentDmesg.txt
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. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Re: DHCP Offer not traversing linux bridge
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
mtu: 9000
bridges:
br-bond0:
addresses:
- 100.126.0.12/23
gateway4: 100.126.0.10
nameservers:
addresses:
- 172.21.12.32
- 172.21.12.62
search: [ "oam.prd.infra.sicredi.net" ]
interfaces:
- bond0
parameters:
forward-delay: 0
priority: 0
stp: false
mtu: 9000
version: 2
I tested with different MTU values with no changes to the result.
These are the interfaces in linux:
2: eno1: mtu 9000 qdisc mq master bond0
state UP group default qlen 1000
link/ether 72:34:88:50:6c:2c brd ff:ff:ff:ff:ff:ff
3: enp22s0f1: mtu 9000 qdisc mq master
bond0 state UP group default qlen 1000
link/ether 72:34:88:50:6c:2c brd ff:ff:ff:ff:ff:ff
6: br-bond0: mtu 9000 qdisc noqueue state UP
group default qlen 1000
link/ether 72:34:88:50:6c:2c brd ff:ff:ff:ff:ff:ff
inet 100.126.0.12/23 brd 100.126.1.255 scope global br-bond0
valid_lft forever preferred_lft forever
inet6 fe80::5018:6cff:fecf:de8a/64 scope link
valid_lft forever preferred_lft forever
32: bond0: mtu 9000 qdisc noqueue
master br-bond0 state UP group default qlen 1000
link/ether 72:34:88:50:6c:2c brd ff:ff:ff:ff:ff:ff
39: tap864c7e54: mtu 9000 qdisc mq master
br-bond0 state UP group default qlen 1000
link/ether ba:a8:b7:fb:e1:00 brd ff:ff:ff:ff:ff:ff
--
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 bridge
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Re: DHCP Offer not traversing linux bridge
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:~$ brctl showstp br-bond0 br-bond0 bridge id 8000.723488506c2c designated root8000.723488506c2c root port 0path cost 0 max age 20.00 bridge max age20.00 hello time2.00 bridge hello time 2.00 forward delay 0.00 bridge forward delay 0.00 ageing time 300.00 hello timer 0.00 tcn timer 0.00 topology change timer 0.00 gc timer 1.32 flags bond0 (1) port id8001stateforwarding designated root8000.723488506c2c path cost 2 designated bridge 8000.723488506c2c message age timer 0.00 designated port8001forward delay timer0.00 designated cost 0hold timer 0.00 flags tap864c7e54 (2) port id8002stateforwarding designated root8000.723488506c2c path cost100 designated bridge 8000.723488506c2c message age timer 0.00 designated port8002forward delay timer0.00 designated cost 0hold timer 0.00 flags -- 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 bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] Re: DHCP Offer not traversing linux bridge
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 bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946028] [NEW] DHCP Offer not traversing linux bridge
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 (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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 bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910866] Re: nvme drive fails after some time
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 focal or if it was always there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
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 to Ubuntu. https://bugs.launchpad.net/bugs/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945707] [NEW] BCM57800 SRIOV bug causes interfaces to disappear
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 "dmesg" no longer show eno3 and eno4 nor any other interface name for these ports. I've read the note in the release notes and this does not appear to be a case of the interface changing names, the 3rd and 4th interface don't show up at all. The card is based on the BCM57800 chipset and has two SFP+ and two gigabit ports on the same card. Commands like "ip link show" no longer show ports 3 and 4. "lspci" still shows four items. dmesg only shows the first two interfaces. This problem seems to be known upstream, and seems to be a regression. More information at https://bugzilla.proxmox.com/show_bug.cgi?id=3558 This is being seen at a customer during an openstack install. It would be appreciated if a workaround could be provided or the fix could be prioritized. Using standard Focal 20.04 LTS kernel (it installs ok with the working kernel then upgrades to the non-working one -- this is done through maas and is difficult to control). Tested other kernels like hwe-* and all seem to be affected too. Client does not want to disable SRIOV on whole card and also cannot disable only ports 3/4 (the bios will not allow it). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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: BCM57800 SRIOV bug causes interfaces to disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940750] [NEW] public key is not available: NO_PUBKEY FCEF32E745F2C3D5
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 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Hit:6 https://download.mono-project.com/repo/ubuntu stable-bionic InRelease Hit:7 https://packages.microsoft.com/ubuntu/18.04/prod bionic InRelease Ign:8 https://pkg.jenkins.io/debian-stable binary/ InRelease Get:9 https://pkg.jenkins.io/debian-stable binary/ Release [2044 B] Get:10 https://pkg.jenkins.io/debian-stable binary/ Release.gpg [833 B] Err:10 https://pkg.jenkins.io/debian-stable binary/ Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FCEF32E745F2C3D5 Fetched 253 kB in 2s (157 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 332 packages can be upgraded. Run 'apt list --upgradable' to see them. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://pkg.jenkins.io/debian-stable binary/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FCEF32E745F2C3D5 W: Failed to fetch https://pkg.jenkins.io/debian-stable/binary/Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FCEF32E745F2C3D5 W: Some index files failed to download. They have been ignored, or old ones used instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu Date: Sat Aug 21 18:17:14 2021 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940750 Title: public key is not available: NO_PUBKEY FCEF32E745F2C3D5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1940750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938068] [NEW] atualização da versão 21.10
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 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon Jul 26 13:45:49 2021 InstallationDate: Installed on 2021-03-18 (129 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to groovy on 2021-07-26 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938068 Title: atualização da versão 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1938068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 306673]
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 still reproduce the situation described in this ticket in a recent and supported software version of Files (nautilus), then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/nautilus/-/issues/ Thank you for your understanding and your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/306673 Title: autofs timeout To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/306673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746146]
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 still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/eog/-/issues/ Thank you for your understanding and your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746146 Title: eog rotate moves small strip of pixels to other side of image To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1746146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
** 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 information failed (-110) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733322]
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 still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new bug report at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/ Thank you for your understanding and your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733322 Title: Unable to enable file or screen sharing with unmanaged network connection To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1733322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-BR] Como fazer normalização de som de um conjunto de áudios?
Olá a todos, bom dia/tarde/noite... É isso aí de cima! Tenho um monte de áudios que preciso colocar como fundo em um quiosque. O problema: os áudios estão cada um com um volume diferente. Como fazer para normalizar, isto é, deixar todos os áudios com o mesmo volume? Já vi que, com o ffmpeg, a gente pode fazer a normalização, mas de um áudio só. Não resolve (e não basta rodar o ffmpeg para todos os áudios). Alguém tem uma ideia? Abraços André Cavalcante Manaus, AM. -- Mais sobre o Ubuntu em português: http://www.ubuntu-br.org/comece Lista de discussão Ubuntu Brasil Histórico, descadastramento e outras opções: https://lists.ubuntu.com/mailman/listinfo/ubuntu-br
[Bug 1900263]
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 still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/gnome-clocks/-/issues/ Thank you for your understanding and your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900263 Title: In Hebrew environment, clock is reversed: minutes are shown before hours To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1900263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853753]
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 ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853753 Title: The toolbar can not be edited To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1853753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 474687] Re: Gthumb needs a way to edit keyboard shortcuts
** 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/474687 Title: Gthumb needs a way to edit keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/gthumb/+bug/474687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766938] Re: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached
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 a year ago. I'm not sure whether this triggered a cache clear or whether the bit depth is different or what... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1766938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766938] Re: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached
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" closed unexpectedly Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers. Press any key to continue... ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+attachment/5478034/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1766938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
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 org.gnome.Shell.desktop[2561]: ** Mar 18 22:42:11 riv18 org.gnome.Shell.desktop[2561]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached Mar 18 22:42:11 riv18 org.gnome.Shell.desktop[2561]: == Stack trace for context 0x55663fe03320 == Mar 18 22:42:11 riv18 gnome-session[2482]: gnome-session-binary[2482]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Mar 18 22:42:11 riv18 gnome-session-binary[2482]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Mar 18 22:42:12 riv18 gsd-media-keys[2649]: g_variant_get_va: assertion 'value != NULL' failed Mar 18 22:42:12 riv18 gsd-media-keys[2649]: g_variant_unref: assertion 'value != NULL' failed Mar 18 22:42:12 riv18 org.gnome.Shell.desktop[2942]: current session already has an ibus-daemon. Mar 18 22:42:12 riv18 dbus-daemon[445]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.178' (uid=1000 pid=2942 comm="/usr/bin/gnome-shell " label="unconfined") Mar 18 22:42:12 riv18 systemd[1]: Starting Location Lookup Service... Mar 18 22:42:13 riv18 dbus-daemon[445]: [system] Successfully activated service 'org.freedesktop.GeoClue2' Mar 18 22:42:13 riv18 systemd[1]: Started Location Lookup Service. Mar 18 22:42:13 riv18 gnome-shell[2942]: Telepathy is not available, chat integration will be disabled. Mar 18 22:42:13 riv18 gsd-media-keys[2649]: g_variant_get_va: assertion 'value != NULL' failed Mar 18 22:42:13 riv18 gsd-media-keys[2649]: g_variant_unref: assertion 'value != NULL' failed Mar 18 22:42:13 riv18 gnome-shell[2942]: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1028]: unreachable code after return statement Mar 18 22:42:13 riv18 org.gnome.Shell.desktop[2942]: ** Mar 18 22:42:13 riv18 org.gnome.Shell.desktop[2942]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908139] Re: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2
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 for both multiple times), however the issue is still present. You say that for you, the problem does not appear under Windows. However, note that (at least in my case) this is a sporadic issue, so it may show up every day or every week or only every one or two months. I know of absolutely no way to predict or even "provoke" this. So are you really sure it is not present for Windows, i. e. have you run the system for MONTHS under Windows and are you sure that your monitors never went off, even for a second or two? I just wanna say that it may be very hard to judge whether this bug is present or not, because it sometimes occurs VERY seldomly. Since I observed it under both Windows 10 and Ubuntu Linux 20.04 LTS and also while in UEFI, I'm pretty sure it is not (only) a software issue. However, I had both motherboard and docking station replaced and it still occurs, suggesting that it may actually be not just a faulty component, but an issue in the actual hardware design, in which case it might affect the entire notebook or even APU series. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908139 Title: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899336] Re: Thinkpad T14s (AMD) external monitors on docking station no longer detected
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 dcn20_program_front_end_for_ctx+0x574/0x580 [amdgpu] [ 4881.023783] Modules linked in: bnep snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi nls_iso8859_1 snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec snd_soc_dmic snd_acp3x_rn snd_hda_core snd_acp3x_pdm_dma soundwire_bus tps6598x snd_soc_core snd_compress ac97_bus iwlmvm snd_pcm_dmaengine btusb edac_mce_amd snd_usb_audio btrtl btbcm snd_seq_midi snd_usbmidi_lib btintel kvm_amd mac80211 snd_seq_midi_event joydev snd_hwdep kvm serio_raw input_leds bluetooth libarc4 snd_rawmidi cdc_ether uvcvideo usbnet snd_pcm snd_seq wmi_bmof ecdh_generic videobuf2_vmalloc r8152 videobuf2_memops ecc videobuf2_v4l2 mii videobuf2_common videodev mc thinkpad_acpi ccp iwlwifi snd_seq_device nvram snd_timer snd_rn_pci_acp3x ledtrig_audio snd_pci_acp3x cfg80211 snd ipmi_devintf ipmi_msghandler ucsi_acpi soundcore typec_ucsi i2c_multi_instantiate typec mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic [ 4881.023814] usbhid hid dm_crypt amdgpu rtsx_pci_sdmmc amd_iommu_v2 crct10dif_pclmul gpu_sched i2c_algo_bit crc32_pclmul ghash_clmulni_intel ttm aesni_intel drm_kms_helper crypto_simd cryptd syscopyarea glue_helper sysfillrect sysimgblt fb_sys_fops cec psmouse rc_core i2c_piix4 drm nvme r8169 rtsx_pci nvme_core realtek wmi video i2c_scmi [ 4881.023834] CPU: 1 PID: 1113 Comm: Xorg Tainted: GW 5.6.0-1048-oem #52-Ubuntu [ 4881.023835] Hardware name: LENOVO 20UH001AGE/20UH001AGE, BIOS R1CET61W(1.30 ) 12/21/2020 [ 4881.023951] RIP: 0010:dcn20_program_front_end_for_ctx+0x574/0x580 [amdgpu] [ 4881.023953] Code: c0 74 cb 4c 89 e2 48 89 df e8 f8 36 dd fa eb be 49 8b 45 00 8b 90 e4 01 00 00 85 d2 75 d5 8b 86 4c 04 00 00 85 c0 75 cb eb a4 <0f> 0b e9 14 fb ff ff 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 [ 4881.023954] RSP: 0018:c087019c7810 EFLAGS: 00010202 [ 4881.023956] RAX: a07c6bec5c00 RBX: a07c6bf5 RCX: 0008 [ 4881.023957] RDX: 0001 RSI: a07bd83e RDI: a07c6bf5 [ 4881.023958] RBP: c087019c7848 R08: 0001 R09: [ 4881.023959] R10: 0001 R11: 0004 R12: a07bd83e [ 4881.023960] R13: a07bd83e01b8 R14: a07bd83e01b8 R15: [ 4881.023962] FS: 7f5369b0ca40() GS:a07c7f84() knlGS: [ 4881.023963] CS: 0010 DS: ES: CR0: 80050033 [ 4881.023964] CR2: 55bf4e2329c8 CR3: 0003f6eb2000 CR4: 00340ee0 [ 4881.023965] Call Trace: [ 4881.024076] dc_commit_state_no_check+0x2cd/0x8a0 [amdgpu] [ 4881.024177] dc_commit_state+0x96/0xb0 [amdgpu] [ 4881.024287] amdgpu_dm_atomic_commit_tail+0x344/0x11d0 [amdgpu] [ 4881.024387] ? amdgpu_cgs_read_register+0x14/0x20 [amdgpu] [ 4881.024484] ? dm_read_reg_func+0x40/0xc0 [amdgpu] [ 4881.024576] ? generic_reg_get+0x22/0x40 [amdgpu] [ 4881.024582] ? _cond_resched+0x19/0x30 [ 4881.024658] ? amdgpu_bo_pin_restricted+0x64/0x2b0 [amdgpu] [ 4881.024665] ? ttm_bo_move_to_lru_tail+0x2d/0xc0 [ttm] [ 4881.024668] ? ww_mutex_unlock+0x26/0x30 [ 4881.024673] ? ttm_eu_backoff_reservation+0x49/0x70 [ttm] [ 4881.024748] ? amdgpu_bo_gpu_offset+0x23/0xa0 [amdgpu] [ 4881.024852] ? dm_plane_helper_prepare_fb+0x143/0x270 [amdgpu] [ 4881.024855] ? _cond_resched+0x19/0x30 [ 4881.024858] ? wait_for_completion_timeout+0x3a/0x120 [ 4881.024859] ? _cond_resched+0x19/0x30 [ 4881.024861] ? wait_for_completion_interruptible+0x37/0x160 [ 4881.024877] commit_tail+0x99/0x130 [drm_kms_helper] [ 4881.024887] drm_atomic_helper_commit+0x123/0x150 [drm_kms_helper] [ 4881.024990] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] [ 4881.025013] drm_atomic_commit+0x4a/0x50 [drm] [ 4881.025031] drm_atomic_connector_commit_dpms+0xdf/0x100 [drm] [ 4881.025051] drm_mode_obj_set_property_ioctl+0x156/0x2d0 [drm] [ 4881.025070] ? drm_connector_set_obj_prop+0x90/0x90 [drm] [ 4881.025086] drm_connector_property_set_ioctl+0x3b/0x60 [drm] [ 4881.025103] drm_ioctl_kernel+0xae/0xf0 [drm] [ 4881.025119] drm_ioctl+0x234/0x3d0 [drm] [ 4881.025134] ? drm_connector_set_obj_prop+0x90/0x90 [drm] [ 4881.025209] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] [ 4881.025213] ksys_ioctl+0x9d/0xd0 [ 4881.025216] __x64_sys_ioctl+0x1a/0x20 [ 4881.025219] do_syscall_64+0x57/0x1b0 [ 4881.025223] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 4881.025225] RIP: 0033:0x7f5369e6c50b [ 4881.025227] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 [ 4881.025228] RSP:
[Bug 1910267] Re: Evolution crash very often doing nothing special ( segfault)
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 special ( segfault) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1910267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
