[Touch-packages] [Bug 2042587] Re: jammy's version breaks existing dhcp scripts with relay
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Fix Committed Bug description: [ Impact ] When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. This was fixed in 2.87, therefore making only jammy carry an affected package. [ Test Plan ] To easily test this on a single machine, a test script is being provided to setup networking and dnsmasq configuration. # Launch a jammy VM lxc launch ubuntu-daily:jammy j-dnsmasq-2042587 --vm # open a root shell in that VM. All subsequent commands must be executed as root in that VM lxc shell j-dnsmasq-2042587 # download test script wget https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+attachment/5738174/+files/setup- and-server.sh # make it executable chmod +x setup-and-server.sh # install dnsmasq. Ignore the postinst error (because systemd-resolved is also running and there is a port conflict) apt update && apt install dnsmasq -y # run the setup script. It will configure things and start dnsmasq ready to be tested ./setup-and-server.sh # in another root session inside the vm (so run "lxc shell j-dnsmasq-2042587" in another terminal), run the proposed commands from the setup script (and press ctrl-c after the result is shown): No DHCP relay: ip netns exec client dhclient -d -v p2 The setup script should log an IP that is not a relay. For example: dnsmasq-dhcp: DHCPDISCOVER(p1) aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPOFFER(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587 ### IP = 192.168.47.150 ### With DHCP relay set to 192.168.47.9, IP should NOT be that address: ip netns exec client dhclient -d -v p2 -g 192.168.47.9 With the affected dnsmasq package, we will see an error: dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587 ### IP = 192.168.47.9 TEST FAILED ### The error is that the obtained IP is that of the dhcp relay (provided via the -g option). With the fixed dnsmasq package, "TEST FAILED" must not appear, and the IP should not be that of the provided dhcp relay. [ Where problems could occur ] If the fix is incorrect, it would mean the dhcp-script would get an incorrect IP again, or perhaps we could have crashes in dnsmasq when dealing with buffers and pointers if the dhcp-script option is in use. This fix was committed upstream a few months after the bug was introduced, so it took a while to be noticed. [ Other Info ] Not at this time. [ Original description ] When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051765] Re: Plymouth FTBFS (even after apt-get build-dep plymouth)
Yes I learned that recently thanks. I'm building it on a noble desktop (no proposed). Just apt-get source plymouth -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2051765 Title: Plymouth FTBFS (even after apt-get build-dep plymouth) Status in plymouth package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Fix Committed Bug description: dh_install dh_install: warning: Cannot find (any matches for) "lib/systemd/system" (tried in ., debian/tmp) dh_install: warning: plymouth missing files: lib/systemd/system dh_install: error: missing files, aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2051765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051765] Re: Plymouth FTBFS (even after apt-get build-dep plymouth)
packages in launchpad always build against -proposed. How are you building this that you're not getting the systemd in proposed? ** Tags removed: regression-release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2051765 Title: Plymouth FTBFS (even after apt-get build-dep plymouth) Status in plymouth package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Fix Committed Bug description: dh_install dh_install: warning: Cannot find (any matches for) "lib/systemd/system" (tried in ., debian/tmp) dh_install: warning: plymouth missing files: lib/systemd/system dh_install: error: missing files, aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2051765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051765] Re: Plymouth FTBFS (even after apt-get build-dep plymouth)
Ah it's because the new systemd (which will fix this) is stuck in proposed. To work around it you need to manually revert: https://launchpadlibrarian.net/709437063/plymouth_23.360.11-0ubuntu1_23.360.11-0ubuntu2.diff.gz ** Changed in: plymouth (Ubuntu) Status: New => In Progress ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Committed ** Changed in: plymouth (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2051765 Title: Plymouth FTBFS (even after apt-get build-dep plymouth) Status in plymouth package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Fix Committed Bug description: dh_install dh_install: warning: Cannot find (any matches for) "lib/systemd/system" (tried in ., debian/tmp) dh_install: warning: plymouth missing files: lib/systemd/system dh_install: error: missing files, aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2051765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
I'm not sure we even need Plymouth installed in initrd because the device_timeout experiment mentioned in comment #18 suggests plymouthd was starting early enough already. It's not the root filesystem that takes too long to appear, but the i915/amdgpu drivers to fully initialize. Also all this talk of SimpleDRM and initrd really belongs more in bug 1965303 and bug 1869655. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
Sorry for the late reply. Proposed package 23.2.1-1ubuntu3.1~22.04.2 amd64 [installed,automatic], GUI displayed normally, thank you for the help! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051540] Re: ufw ftbfs with Python 3.12 as default
** Also affects: ufw
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Status in ufw:
New
Status in ufw package in Ubuntu:
Confirmed
Bug description:
==
ERROR: test_ufwcommand_parse
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
Test UFWCommand.parse()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in
test_ufwcommand_parse
self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
==
ERROR: test_ufwcommand_rule_get_command
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
Test UFWCommand(Route)Rule.get_command()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in
test_ufwcommand_rule_get_command
self.assertEquals(len(errors), 0,
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
--
Ran 24 tests in 7.584s
FAILED (errors=9)
test_skeleton
test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
Test example dummy test ... ok
--
Ran 1 test in 0.000s
OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/2051540/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051540] Re: ufw ftbfs with Python 3.12 as default
** Merge proposal linked:
https://code.launchpad.net/~alexmurray/ufw/+git/ufw/+merge/459690
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Status in ufw:
New
Status in ufw package in Ubuntu:
Confirmed
Bug description:
==
ERROR: test_ufwcommand_parse
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
Test UFWCommand.parse()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in
test_ufwcommand_parse
self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
==
ERROR: test_ufwcommand_rule_get_command
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
Test UFWCommand(Route)Rule.get_command()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in
test_ufwcommand_rule_get_command
self.assertEquals(len(errors), 0,
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
--
Ran 24 tests in 7.584s
FAILED (errors=9)
test_skeleton
test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
Test example dummy test ... ok
--
Ran 1 test in 0.000s
OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/2051540/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2050831] Re: Performance
Thanks for the bug report. It appears the graphics driver and Xorg are working correctly here. And certainly I would not expect all modern games to maintain 60 FPS on the integrated GPU of an Intel i3-1115G4. As for the blurry HDMI output, the Samsung un32t4300 is limited to 1366x768 so a little blurry compared to the laptop screen is probably correct. Can you please plug the TV in again and then run: xrandr --verbose > xrandr.txt and attach the resulting text file here? Also please try to report only one problem per bug report. You can log many separate bug reports. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2050831 Title: Performance Status in Ubuntu: Incomplete Bug description: Hello, inside Steam, in big picture mode, in system, system information, the vram memory has a negative value, it is not showing the real amount that the onboard reaches, supports. I think it's the video driver, or some other driver. There are also some fps losses, games that reach 60fps, at various times it is below, like 45fps or less. Even switching to maximum performance mode by clicking on the system battery icon. When I connect the PC to a smart TV as the primary screen, with HDMI, full HD, the image is blurry, as if there were blurs in the images. In the TV settings, it is set to maximum contrast and sharpness. Also another feedback: in languages, in the system settings, I can't download the missing packages, the download button is not shown. This happens after installing the system in minimal mode, and then installing other additional programs. I will send the name of the programs. sudo apt install --install-recommends guvcview rhythmbox libreoffice psensor Lenovo Ideapad 3 15itl6 82md Linux Kubuntu lts 22.04 Kde plasma 1920x1080p 60hz 4gb ram 20gb swap btfrs ptbr utf8 abnt2 Steam (.deb), from the Steam website. samsung smarttv, 32 inches, un32t4300 In the system settings, on monitor, the scale is at 100% Thank you in advance, success always ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Jan 22 17:09:37 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a78] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f9c] InstallationDate: Installed on 2024-01-13 (9 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: LENOVO 82MD ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-14-generic root=UUID=58277c11-b933-4491-8d44-0caa0d498477 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2023 dmi.bios.release: 1.57 dmi.bios.vendor: LENOVO dmi.bios.version: GGCN57WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ITL6 dmi.ec.firmware.release: 1.57 dmi.modalias: dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6: dmi.product.family: IdeaPad 3 15ITL6 dmi.product.name: 82MD dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6 dmi.product.version: IdeaPad 3 15ITL6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2050831/+subscriptions -- Mailing
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
> I belive /usr/share/initrams-tools/hooks/plymouth can be modified to stop > including any > drm modules and /usr/share/initramfs-tools/framebuffer can be totally dropped. Dropping the DRM modules would also allow us to use a near-zero device_timeout in Plymouth now. It would then render to efifb without needing SimpleDRM. I don't *think* this would affect shutdown because plymouthd for that is started while we still have the rootfs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051694] Re: Regression: Kubuntu 22.04 LTS overrides Xorg.conf-specified monitor layout
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2051694
Title:
Regression: Kubuntu 22.04 LTS overrides Xorg.conf-specified monitor
layout
Status in xorg-server package in Ubuntu:
New
Bug description:
When I built a new PC with Kubuntu 22.04 LTS, I carried over my
recently purchased GeForce RTX 3060 and copied over the Xorg.conf that
was doing perfectly well for me in 20.04 LTS, containing the following
line:
Option "metamodes" "HDMI-0: 1280x1024 +3200+0, DP-3:
1280x1024 +0+0, DP-1: 1920x1080 +1280+0"
(Bear in mind that, due to a history of bugginess in KScreen2 and how
it interacts with Plasma panel layouts, I disable it in the Background
Services control panel and do my best to lock down the allowed layouts
and resolutions in Xorg.conf.)
This technique has been working for me for close to a decade, with my
previous video card being a GeForce GTX750 and, if I remember
correctly, I was also using it with the GeForce GT430 I was using
before that, and with Kubuntu and Lubuntu versions going back to at
least Kubuntu 16.04 LTS and likely to Lubuntu 14.04 and possibly even
Lubuntu 12.04.
However, much to my dismay, it appeared to have no effect, and the
system was still assigning a virtual layout that didn't match the
physical arrangement of the monitors.
Eventually, I realized from /var/log/Xorg.0.log that my metamodes line
WAS getting set, but, for reasons I still have no idea how to
diagnose, something else was overriding it and resetting the metamodes
line back to the undesired default, with unlocked resolutions and an
incorrect monitor layout.
[21.689] (II) NVIDIA(0): Setting mode "HDMI-0: 1280x1024 @1280x1024
+3200+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3: 1280x1024
@1280x1024 +0+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-1:
nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}"
[21.747] (II) NVIDIA(0): Setting mode "DP-3: 1280x1024 @1280x1024 +0+0
{ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-1: nvidia-auto-select
@1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[21.834] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select
@1280x1024 +1920+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3:
1280x1024 @1280x1024 +0+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0},
DP-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}"
[21.922] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select
@1280x1024 +1920+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3:
nvidia-auto-select @1280x1024 +3200+0 {ViewPortIn=1280x1024,
ViewPortOut=1280x1024+0+0}, DP-1: nvidia-auto-select @1920x1080 +0+0
{ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
As a workaround which may or may not show up in the ubuntu-bug report,
I've created a /etc/X11/Xsession.d/01-fix-the-damn-ignored-metamodes
file containing the line `xrandr --output DP-3 --left-of DP-1`.
...though that doesn't fix the monitor layout at the login screen and
it's not possible to work around the forced changeability of the
resolution without a working metamodes according to
https://gitlab.freedesktop.org/xorg/xserver/-/issues/353#note_91110
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.146.02 Sun Dec 3
14:06:14 UTC 2023
GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: KDE
Date: Tue Jan 30 06:25:44 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GA106 [GeForce RTX 3060 Lite Hash Rate]
[1043:8810]
Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c6) (prog-if
00 [VGA controller])
Subsystem: Advanced
[Touch-packages] [Bug 2051711] Re: Ubuntu Freezes
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2051711 Title: Ubuntu Freezes Status in Ubuntu: Incomplete Bug description: Likely - problem with graphical card driver ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/g/gcc-12/cpp-12_12.1.0-2ubuntu1~22.04_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-gl-515_515.86.01-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-gl-525_525.78.01-0ubuntu0.22.04.1_amd64.deb CasperMD5CheckResult: fail CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 30 16:29:33 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22e8] InstallationDate: Installed on 2023-07-10 (204 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 21AH0092CK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=5a82ce67-8314-4e81-9866-eaaf4c03e725 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2022 dmi.bios.release: 1.2 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET05W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AH0092CK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrN3MET05W(1.02):bd06/07/2022:br1.2:efr1.3:svnLENOVO:pn21AH0092CK:pvrThinkPadT14Gen3:rvnLENOVO:rn21AH0092CK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21AH_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21AH0092CK dmi.product.sku: LENOVO_MT_21AH_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2051711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Thanks. So it still sounds like SimpleDRM is in Ubuntu's future (bug 1965303). But in case that doesn't happen in time for Noble, or if we simply want a solution that backports to jammy, then I will still focus on plymouth/kernel changes only. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Yeah; so try forcing plymouth to the Ubuntu initrd like this: echo "FRAMEBUFFER=y" | sudo tee /etc/initramfs-tools/conf.d/splash Then if you rebuild the initrd you'll end up with plymouth in it. This unfortunately DOUBLES the initramfs size; but it's because it puts all the drm modules in there. Here is where simpledrm really shines. I belive /usr/share/initrams-tools/hooks/plymouth can be modified to stop including any drm modules and /usr/share/initramfs-tools/framebuffer can be totally dropped. I believe this will guarantee plymouth wins the race. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Something "big" I notice different is that by default Ubuntu doesn't put plymouth in the initramfs but Fedora does. Maybe plymouthd really isn't running at the time systemd-fsckd is running. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
> I don't really know if Fedora does that better or they just failed to notice the bug. I have Fedora 39 and Ubuntu both set up on a Z13 and Plymouth comes up in Fedora with simpledrm; never see the console. That's why I was thinking something might be missing and worth looking at. * Fedora doesn't key off "splash", they key off "rhgb" (standing for red hat graphical boot). * Ubuntu sets "vt.handoff=7", Fedora doesn't do anything. Maybe it's part of this flow difference leading to the problem? That's from ~10 years ago, does it still make sense? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
On Tue, Jan 30, 2024 at 6:21 PM Michael Hudson-Doyle <2045...@bugs.launchpad.net> wrote: > > Oh wait, we've been through something very like this before > https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875. I suspect > a judicious application of flock may be the most correct solution > available. ACK - I'll switch over to flock and run another test. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
"splash" is more appropriate than "quiet" (unfortunately) because we would delay framebuffer takeover to the same event (primary DRM startup) as Plymouth does. I would also like to know why our Plymouth doesn't render on SimpleDRM even when it's available (tested in bug 1965303). I don't really know if Fedora does that better or they just failed to notice the bug. And I don't have much time left for more tangents here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Have you already looked at everything Fedora is doing in this area? They already have simpledrm; but from what you described I would have thought they should still lose the fbcon race. Is it just that they don't have systemd-fsckd patch? I would think they still end up showing ERR/WARN kernel messages which can be noisy too. Just wondering if there is something else to look at. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
> But the feature would still be gated on the "splash" kernel parameter which is Plymouth-specific and may cause pushback from kernel developers. If the patch is the way you go another idea for you is to use the "quiet" keyword to key off instead for this behavior which is already used by the kernel. You'd be overloading it. quiet [KNL] Disable most log messages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051705] Re: Failed to start bluetooth.service: Unit bluetooth.service failed to load properly, please adjust/correct and reload service manager: File exists
It looks like the installation might have succeeded and just requires a
reboot. The error was:
Failed to start bluetooth.service: Unit bluetooth.service failed to load
properly, please adjust/correct and reload service manager: File exists
** Summary changed:
- package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed bluez
package post-installation script subprocess returned error exit status 1
+ Failed to start bluetooth.service: Unit bluetooth.service failed to load
properly, please adjust/correct and reload service manager: File exists
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2051705
Title:
Failed to start bluetooth.service: Unit bluetooth.service failed to
load properly, please adjust/correct and reload service manager: File
exists
Status in bluez package in Ubuntu:
New
Bug description:
I am unable to turn on my Bluetooth so I unable to connect to my mouse
and earbuds to laptops
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1.1
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
bluez:amd64: Install
python3-gi-cairo:amd64: Install
blueman:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Jan 30 20:30:22 2024
ErrorMessage: installed bluez package post-installation script subprocess
returned error exit status 1
InstallationDate: Installed on 2023-07-28 (186 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera
Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-15-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.22.0ubuntu1
apt 2.7.3
SnapChanges:
ID Status Spawn Ready Summary
115 Done2024-01-30T20:08:13+05:30 2024-01-30T20:09:04+05:30 Install
"bluez" snap
SourcePackage: bluez
Title: package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed
bluez package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-11-20 (71 days ago)
dmi.bios.date: 06/13/2018
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: 8TCN44WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 330-15IKB
dmi.ec.firmware.release: 1.44
dmi.modalias:
dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:br1.44:efr1.44:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81DE_BU_idea_FM_ideapad330-15IKB:
dmi.product.family: ideapad 330-15IKB
dmi.product.name: 81DE
dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB
dmi.product.version: Lenovo ideapad 330-15IKB
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: 20:16:B9:30:5F:51 ACL MTU: 1021:5 SCO MTU: 96:6
DOWN
RX bytes:20039 acl:61 sco:0 events:2513 errors:0
TX bytes:1443881 acl:2245 sco:0 commands:251 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2051705/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
I now expect the kernel patch would change before it gets proposed to dri-devel. In particular the primary delay doesn't need to be configurable (or even finite?), and the secondary delay probably doesn't need to be more than zero. But the feature would still be gated on the "splash" kernel parameter which is Plymouth-specific and may cause pushback from kernel developers. It's starting to make more sense to implement the console disabling using ioctls in plymouthd itself. Because I think plymouthd is running early enough to do that, it's only refusing to render for several seconds so fbcon wins the race to the framebuffer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Changed in: plymouth (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
Oh wait, we've been through something very like this before https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875. I suspect a judicious application of flock may be the most correct solution available. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
I am also the author of the Plymouth feature that parses and renders the fsck progress. What I think isn't being communicated here is that it's currently useless on startup. Because Plymouth doesn't start rendering until well after the fsck has already happened. See also bug 1869655. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051031] Re: Occasionally system alert will play as loud scary static noise.
Happened twice today I swear this is going to give some one a heart attack -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2051031 Title: Occasionally system alert will play as loud scary static noise. Status in alsa-driver package in Ubuntu: New Bug description: EG when I made this issue I was trying to autocomplete a scp command in my terminal. The autocomplete noise was a scary static noise.. litterlly like something out of a horror movie and it's very jarring. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.1.0-1027.27-oem 6.1.61 Uname: Linux 6.1.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 14:37:35 2024 InstallationDate: Installed on 2023-12-05 (49 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Blackjack successful Symptom_Card: BRIO Ultra HD Webcam - Logitech BRIO Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [USB-Audio - Onyx Blackjack, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA73433005D dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed
** Description changed: In removing the LXD snap from preseeding in the server seed for Ubuntu - 24.04 as part LP #2051346 [1] we also removed the snaps snap and the + 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. - - Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded + Time taken to install LXD snap using the lxd-installer package without + snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` - - Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. + Time taken to install LXD snap using the lxd-installer package with + snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re-introduce core22 and snaps snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 - [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 ** Description changed: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re-introduce - core22 and snaps snaps to our seed. + core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1]
[Touch-packages] [Bug 2051711] [NEW] Ubuntu Freezes
Public bug reported: Likely - problem with graphical card driver ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/g/gcc-12/cpp-12_12.1.0-2ubuntu1~22.04_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-gl-515_515.86.01-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-gl-525_525.78.01-0ubuntu0.22.04.1_amd64.deb CasperMD5CheckResult: fail CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 30 16:29:33 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22e8] InstallationDate: Installed on 2023-07-10 (204 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 21AH0092CK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=5a82ce67-8314-4e81-9866-eaaf4c03e725 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2022 dmi.bios.release: 1.2 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET05W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AH0092CK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrN3MET05W(1.02):bd06/07/2022:br1.2:efr1.3:svnLENOVO:pn21AH0092CK:pvrThinkPadT14Gen3:rvnLENOVO:rn21AH0092CK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21AH_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21AH0092CK dmi.product.sku: LENOVO_MT_21AH_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2051711 Title: Ubuntu Freezes Status in xorg package in Ubuntu: New Bug description: Likely - problem with graphical card driver ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/g/gcc-12/cpp-12_12.1.0-2ubuntu1~22.04_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-gl-515_515.86.01-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-gl-525_525.78.01-0ubuntu0.22.04.1_amd64.deb CasperMD5CheckResult: fail CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 30 16:29:33 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22e8] InstallationDate: Installed on 2023-07-10 (204 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 21AH0092CK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=5a82ce67-8314-4e81-9866-eaaf4c03e725 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2022 dmi.bios.release: 1.2 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET05W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AH0092CK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.3 dmi.modalias:
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
AFAIK, the systemd-fsckd patch is still required, but we have vague plans to get rid of it by making plymouth learn this functionality (i.e. reading /run/systemd/fsck.progress directly). I have no idea about the re-ordering, but it would be easy to test with a drop-in config. ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051709] [NEW] package linux-image-5.15.0-92-generic 5.15.0-92.102 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: I feel like this was due to storage available at the time of the virtual build. As it hit capacity, it started to throws errors. I have since adjusted allotted space to 40GB from the default. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-92-generic 5.15.0-92.102 ProcVersionSignature: Ubuntu 6.2.0-1019.19~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1019-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-modules-extra-5.15.0-92-generic:amd64: Install linux-headers-5.15.0-92:amd64: Install NULL: ConfigurePending Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Mon Jan 29 10:07:21 2024 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1019-azure root=UUID=89ee03ba-6808-4977-a4fb-9b10174744f8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.15.0-92-generic 5.15.0-92.102 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2022 dmi.bios.release: 4.1 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.1 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.1 dmi.chassis.asset.tag: 6076-2812-1301-1065-6309-1370-01 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.1 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd04/06/2022:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.1 dmi.sys.vendor: Microsoft Corporation ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2051709 Title: package linux-image-5.15.0-92-generic 5.15.0-92.102 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I feel like this was due to storage available at the time of the virtual build. As it hit capacity, it started to throws errors. I have since adjusted allotted space to 40GB from the default. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-92-generic 5.15.0-92.102 ProcVersionSignature: Ubuntu 6.2.0-1019.19~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1019-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-modules-extra-5.15.0-92-generic:amd64: Install linux-headers-5.15.0-92:amd64: Install NULL: ConfigurePending Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Mon Jan 29 10:07:21 2024 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1019-azure root=UUID=89ee03ba-6808-4977-a4fb-9b10174744f8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.15.0-92-generic 5.15.0-92.102 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
[Touch-packages] [Bug 2051705] Re: package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2051705
Title:
package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed
bluez package post-installation script subprocess returned error exit
status 1
Status in bluez package in Ubuntu:
New
Bug description:
I am unable to turn on my Bluetooth so I unable to connect to my mouse
and earbuds to laptops
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1.1
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
bluez:amd64: Install
python3-gi-cairo:amd64: Install
blueman:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Jan 30 20:30:22 2024
ErrorMessage: installed bluez package post-installation script subprocess
returned error exit status 1
InstallationDate: Installed on 2023-07-28 (186 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera
Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-15-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.22.0ubuntu1
apt 2.7.3
SnapChanges:
ID Status Spawn Ready Summary
115 Done2024-01-30T20:08:13+05:30 2024-01-30T20:09:04+05:30 Install
"bluez" snap
SourcePackage: bluez
Title: package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed
bluez package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-11-20 (71 days ago)
dmi.bios.date: 06/13/2018
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: 8TCN44WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 330-15IKB
dmi.ec.firmware.release: 1.44
dmi.modalias:
dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:br1.44:efr1.44:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81DE_BU_idea_FM_ideapad330-15IKB:
dmi.product.family: ideapad 330-15IKB
dmi.product.name: 81DE
dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB
dmi.product.version: Lenovo ideapad 330-15IKB
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: 20:16:B9:30:5F:51 ACL MTU: 1021:5 SCO MTU: 96:6
DOWN
RX bytes:20039 acl:61 sco:0 events:2513 errors:0
TX bytes:1443881 acl:2245 sco:0 commands:251 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2051705/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051705] [NEW] package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
Public bug reported:
I am unable to turn on my Bluetooth so I unable to connect to my mouse
and earbuds to laptops
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1.1
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
bluez:amd64: Install
python3-gi-cairo:amd64: Install
blueman:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Jan 30 20:30:22 2024
ErrorMessage: installed bluez package post-installation script subprocess
returned error exit status 1
InstallationDate: Installed on 2023-07-28 (186 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera
Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-15-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.22.0ubuntu1
apt 2.7.3
SnapChanges:
ID Status Spawn Ready Summary
115 Done2024-01-30T20:08:13+05:30 2024-01-30T20:09:04+05:30 Install
"bluez" snap
SourcePackage: bluez
Title: package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed bluez
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-11-20 (71 days ago)
dmi.bios.date: 06/13/2018
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: 8TCN44WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 330-15IKB
dmi.ec.firmware.release: 1.44
dmi.modalias:
dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:br1.44:efr1.44:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81DE_BU_idea_FM_ideapad330-15IKB:
dmi.product.family: ideapad 330-15IKB
dmi.product.name: 81DE
dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB
dmi.product.version: Lenovo ideapad 330-15IKB
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 20:16:B9:30:5F:51 ACL MTU: 1021:5 SCO MTU: 96:6
DOWN
RX bytes:20039 acl:61 sco:0 events:2513 errors:0
TX bytes:1443881 acl:2245 sco:0 commands:251 errors:0
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package mantic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2051705
Title:
package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed
bluez package post-installation script subprocess returned error exit
status 1
Status in bluez package in Ubuntu:
New
Bug description:
I am unable to turn on my Bluetooth so I unable to connect to my mouse
and earbuds to laptops
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1.1
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
bluez:amd64: Install
python3-gi-cairo:amd64: Install
blueman:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Jan 30 20:30:22 2024
ErrorMessage: installed bluez package post-installation script subprocess
returned error exit status 1
InstallationDate: Installed on 2023-07-28 (186 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera
Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-15-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.22.0ubuntu1
apt 2.7.3
SnapChanges:
ID Status Spawn Ready Summary
115 Done
[Touch-packages] [Bug 2050831] Re: Performance
ok, thanks, success always -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2050831 Title: Performance Status in xorg package in Ubuntu: New Bug description: Hello, inside Steam, in big picture mode, in system, system information, the vram memory has a negative value, it is not showing the real amount that the onboard reaches, supports. I think it's the video driver, or some other driver. There are also some fps losses, games that reach 60fps, at various times it is below, like 45fps or less. Even switching to maximum performance mode by clicking on the system battery icon. When I connect the PC to a smart TV as the primary screen, with HDMI, full HD, the image is blurry, as if there were blurs in the images. In the TV settings, it is set to maximum contrast and sharpness. Also another feedback: in languages, in the system settings, I can't download the missing packages, the download button is not shown. This happens after installing the system in minimal mode, and then installing other additional programs. I will send the name of the programs. sudo apt install --install-recommends guvcview rhythmbox libreoffice psensor Lenovo Ideapad 3 15itl6 82md Linux Kubuntu lts 22.04 Kde plasma 1920x1080p 60hz 4gb ram 20gb swap btfrs ptbr utf8 abnt2 Steam (.deb), from the Steam website. samsung smarttv, 32 inches, un32t4300 In the system settings, on monitor, the scale is at 100% Thank you in advance, success always ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Jan 22 17:09:37 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a78] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f9c] InstallationDate: Installed on 2024-01-13 (9 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: LENOVO 82MD ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-14-generic root=UUID=58277c11-b933-4491-8d44-0caa0d498477 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2023 dmi.bios.release: 1.57 dmi.bios.vendor: LENOVO dmi.bios.version: GGCN57WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ITL6 dmi.ec.firmware.release: 1.57 dmi.modalias: dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6: dmi.product.family: IdeaPad 3 15ITL6 dmi.product.name: 82MD dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6 dmi.product.version: IdeaPad 3 15ITL6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2050831/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051405] Re: ProtectHome setting in debian/rsyslog.service isn't understood by systemd
Merge request https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/459640 ** Changed in: rsyslog (Ubuntu) Assignee: Heinrich Schuchardt (xypron) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2051405 Title: ProtectHome setting in debian/rsyslog.service isn't understood by systemd Status in rsyslog package in Ubuntu: Confirmed Bug description: Small bug introduced in commit e175f5c3668adc1c65f66efb61f70060569c9fe8 https://git.launchpad.net/ubuntu/+source/rsyslog/commit/?id=e175f5c3668adc1c65f66efb61f70060569c9fe8 which changed the rsyslog.service line of ProtectHome=yes to ProtectHome=readonly Systemd doesn't understand "readonly" https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html and will mention in its journal: systemd[1]: /lib/systemd/system/rsyslog.service:24: Failed to parse protect home value, ignoring: readonly Quickfix: just needs a hyphen on line 24 to read 'read-only' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2051405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008491] Re: Memory leak in pulseaudio
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2008491 Title: Memory leak in pulseaudio Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is very weird, but my pulseaudio uses 3.5GB as I type this. That seems big for audio stuff. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 14:56:46 2023 InstallationDate: Installed on 2023-01-04 (51 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.23:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2008491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026885] Re: nano is not available on i386
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/2026885 Title: nano is not available on i386 Status in nano package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: There is no i386 Nano package in Jammy. I used Nano all the time including in chroots, which is where this reared its ugly head. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/2026885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051350] Re: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is dif
** Package changed: ubuntu => alsa-plugins (Ubuntu) ** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/2051350 Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio- default.conf.example', which is different from other instances of package libasound2-plugins:i386 Status in alsa-plugins package in Ubuntu: New Bug description: wa installing wine ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libasound2-plugins 1.2.7.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15.1-lowlatency 6.5.3 Uname: Linux 6.5.0-15-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 26 10:23:45 2024 DuplicateSignature: package:libasound2-plugins:1.2.7.1-1ubuntu2 Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-LCQD0p/134-libasound2-plugins_1.2.7.1-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 ErrorMessage: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 InstallationDate: Installed on 2024-01-25 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: alsa-plugins Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/2051350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2050831] Re: Performance
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2050831 Title: Performance Status in xorg package in Ubuntu: New Bug description: Hello, inside Steam, in big picture mode, in system, system information, the vram memory has a negative value, it is not showing the real amount that the onboard reaches, supports. I think it's the video driver, or some other driver. There are also some fps losses, games that reach 60fps, at various times it is below, like 45fps or less. Even switching to maximum performance mode by clicking on the system battery icon. When I connect the PC to a smart TV as the primary screen, with HDMI, full HD, the image is blurry, as if there were blurs in the images. In the TV settings, it is set to maximum contrast and sharpness. Also another feedback: in languages, in the system settings, I can't download the missing packages, the download button is not shown. This happens after installing the system in minimal mode, and then installing other additional programs. I will send the name of the programs. sudo apt install --install-recommends guvcview rhythmbox libreoffice psensor Lenovo Ideapad 3 15itl6 82md Linux Kubuntu lts 22.04 Kde plasma 1920x1080p 60hz 4gb ram 20gb swap btfrs ptbr utf8 abnt2 Steam (.deb), from the Steam website. samsung smarttv, 32 inches, un32t4300 In the system settings, on monitor, the scale is at 100% Thank you in advance, success always ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Jan 22 17:09:37 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a78] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f9c] InstallationDate: Installed on 2024-01-13 (9 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: LENOVO 82MD ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-14-generic root=UUID=58277c11-b933-4491-8d44-0caa0d498477 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2023 dmi.bios.release: 1.57 dmi.bios.vendor: LENOVO dmi.bios.version: GGCN57WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ITL6 dmi.ec.firmware.release: 1.57 dmi.modalias: dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6: dmi.product.family: IdeaPad 3 15ITL6 dmi.product.name: 82MD dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6 dmi.product.version: IdeaPad 3 15ITL6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2050831/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 2051350] [NEW] package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is d
You have been subscribed to a public bug: wa installing wine ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libasound2-plugins 1.2.7.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15.1-lowlatency 6.5.3 Uname: Linux 6.5.0-15-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 26 10:23:45 2024 DuplicateSignature: package:libasound2-plugins:1.2.7.1-1ubuntu2 Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-LCQD0p/134-libasound2-plugins_1.2.7.1-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 ErrorMessage: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 InstallationDate: Installed on 2024-01-25 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: alsa-plugins Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package mantic need-duplicate-check package-conflict -- package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 https://bugs.launchpad.net/bugs/2051350 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051694] [NEW] Regression: Kubuntu 22.04 LTS overrides Xorg.conf-specified monitor layout
Public bug reported:
When I built a new PC with Kubuntu 22.04 LTS, I carried over my recently
purchased GeForce RTX 3060 and copied over the Xorg.conf that was doing
perfectly well for me in 20.04 LTS, containing the following line:
Option "metamodes" "HDMI-0: 1280x1024 +3200+0, DP-3:
1280x1024 +0+0, DP-1: 1920x1080 +1280+0"
(Bear in mind that, due to a history of bugginess in KScreen2 and how it
interacts with Plasma panel layouts, I disable it in the Background
Services control panel and do my best to lock down the allowed layouts
and resolutions in Xorg.conf.)
This technique has been working for me for close to a decade, with my
previous video card being a GeForce GTX750 and, if I remember correctly,
I was also using it with the GeForce GT430 I was using before that, and
with Kubuntu and Lubuntu versions going back to at least Kubuntu 16.04
LTS and likely to Lubuntu 14.04 and possibly even Lubuntu 12.04.
However, much to my dismay, it appeared to have no effect, and the
system was still assigning a virtual layout that didn't match the
physical arrangement of the monitors.
Eventually, I realized from /var/log/Xorg.0.log that my metamodes line
WAS getting set, but, for reasons I still have no idea how to diagnose,
something else was overriding it and resetting the metamodes line back
to the undesired default, with unlocked resolutions and an incorrect
monitor layout.
[21.689] (II) NVIDIA(0): Setting mode "HDMI-0: 1280x1024 @1280x1024 +3200+0
{ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3: 1280x1024 @1280x1024
+0+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-1:
nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}"
[21.747] (II) NVIDIA(0): Setting mode "DP-3: 1280x1024 @1280x1024 +0+0
{ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-1: nvidia-auto-select
@1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[21.834] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select
@1280x1024 +1920+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3:
1280x1024 @1280x1024 +0+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0},
DP-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}"
[21.922] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select
@1280x1024 +1920+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3:
nvidia-auto-select @1280x1024 +3200+0 {ViewPortIn=1280x1024,
ViewPortOut=1280x1024+0+0}, DP-1: nvidia-auto-select @1920x1080 +0+0
{ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
As a workaround which may or may not show up in the ubuntu-bug report,
I've created a /etc/X11/Xsession.d/01-fix-the-damn-ignored-metamodes
file containing the line `xrandr --output DP-3 --left-of DP-1`.
...though that doesn't fix the monitor layout at the login screen and
it's not possible to work around the forced changeability of the
resolution without a working metamodes according to
https://gitlab.freedesktop.org/xorg/xserver/-/issues/353#note_91110
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.146.02 Sun Dec 3
14:06:14 UTC 2023
GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: KDE
Date: Tue Jan 30 06:25:44 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GA106 [GeForce RTX 3060 Lite Hash Rate]
[1043:8810]
Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c6) (prog-if 00
[VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e]
InstallationDate: Installed on 2024-01-05 (24 days ago)
InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.1)
MachineType: ASRock B650 PG Lightning
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=7aefb7ca-223b-4111-81e4-0d2a1003dbce ro
zfs.zfs_dmu_offset_next_sync=0 quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
[Touch-packages] [Bug 1887655] Re: unattended-upgrades triggers reboot despite configuration
I can confirm this behavior on our server with Ubuntu Server 20.04. The
occurence is random and the symptoms and log information is the same.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1887655
Title:
unattended-upgrades triggers reboot despite configuration
Status in unattended-upgrades package in Ubuntu:
Confirmed
Bug description:
I've been having problems with my Ubuntu machine suddenly rebooting
without any warning. To my knowledge Ubuntu Desktop is not supposed
to reboot without warning by default.
I believe this is being triggered by unattended-upgrades
unattended-upgrades 2.3 (amd64)
Ubuntu Desktop:
Description: Ubuntu 20.04 LTS
Release: 20.04
One pattern that emerges is that the reboot happens right after
unattended-upgrades completes successfully. There are multiple
examples in my /var/log/syslog, but all show "unattended-
upgrades.service: Succeeded." the same second everything begins to
shut down, with nothing for a minute or two prior. Example:
Jul 15 11:17:01 pc systemd[2065]: Starting Notification regarding a new
release of Ubuntu...
Jul 15 11:17:14 pc charon: 08[IKE] sending keep alive to 10.10.10.10[4500]
Jul 15 11:17:22 pc check-new-release-gtk[71843]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:30: PyGIWarning: Gtk was
imported without specifying a version first. Use gi.require_version('Gtk'
, '3.0') before import to ensure that the right version gets loaded.
Jul 15 11:17:22 pc check-new-release-gtk[71843]: from gi.repository import
Gtk
Jul 15 11:17:22 pc check-new-release-gtk[71843]: WARNING:root:timeout
reached, exiting
Jul 15 11:17:22 pc systemd[2065]: update-notifier-release.service: Succeeded.
Jul 15 11:17:22 pc systemd[2065]: Finished Notification regarding a new
release of Ubuntu.
Jul 15 11:17:48 pc mysql-workbench[33350]: gtk_tree_view_unref_tree_helper:
assertion 'node != NULL' failed
Jul 15 11:17:54 pc charon: 09[IKE] sending keep alive to 10.10.10.10[4500]
Jul 15 11:18:03 pc systemd[1]: unattended-upgrades.service: Succeeded.
Jul 15 11:18:03 pc systemd[1]: Stopping Session 3 of user philip.
Jul 15 11:18:03 pc systemd[1]: Removed slice
system-clean\x2dmount\x2dpoint.slice.
Jul 15 11:18:03 pc systemd[1]: Removed slice system-getty.slice.
Jul 15 11:18:03 pc systemd[1]: Removed slice system-modprobe.slice.
Jul 15 11:18:03 pc systemd[1]: Stopped target Block Device Preparation for
/dev/mapper/ubuntu.
Jul 15 11:18:03 pc systemd[2065]: Stopped target GNOME Wayland Session
(session: gnome).
From memory I've never edited the contents of /etc/apt/apt.conf.d/ and
the configuration for unattended upgrades claims to be default (NOT to
reboot):
$ grep -irnC4 reboot /etc/apt/apt.conf.d/
/etc/apt/apt.conf.d/50unattended-upgrades-88-// Do automatic removal of
unused packages after the upgrade
/etc/apt/apt.conf.d/50unattended-upgrades-89-// (equivalent to apt-get
autoremove)
/etc/apt/apt.conf.d/50unattended-upgrades-90-//Unattended-Upgrade::Remove-Unused-Dependencies
"false";
/etc/apt/apt.conf.d/50unattended-upgrades-91-
/etc/apt/apt.conf.d/50unattended-upgrades:92:// Automatically reboot *WITHOUT
CONFIRMATION* if
/etc/apt/apt.conf.d/50unattended-upgrades:93:// the file
/var/run/reboot-required is found after the upgrade
/etc/apt/apt.conf.d/50unattended-upgrades:94://Unattended-Upgrade::Automatic-Reboot
"false";
/etc/apt/apt.conf.d/50unattended-upgrades-95-
/etc/apt/apt.conf.d/50unattended-upgrades:96:// Automatically reboot even if
there are users currently logged in
/etc/apt/apt.conf.d/50unattended-upgrades:97:// when
Unattended-Upgrade::Automatic-Reboot is set to true
/etc/apt/apt.conf.d/50unattended-upgrades:98://Unattended-Upgrade::Automatic-Reboot-WithUsers
"true";
/etc/apt/apt.conf.d/50unattended-upgrades-99-
/etc/apt/apt.conf.d/50unattended-upgrades:100:// If automatic reboot is
enabled and needed, reboot at the specific
/etc/apt/apt.conf.d/50unattended-upgrades-101-// time instead of immediately
/etc/apt/apt.conf.d/50unattended-upgrades-102-// Default: "now"
/etc/apt/apt.conf.d/50unattended-upgrades:103://Unattended-Upgrade::Automatic-Reboot-Time
"02:00";
/etc/apt/apt.conf.d/50unattended-upgrades-104-
/etc/apt/apt.conf.d/50unattended-upgrades-105-// Use apt bandwidth limit
feature, this example limits the download
/etc/apt/apt.conf.d/50unattended-upgrades-106-// speed to 70kb/sec
/etc/apt/apt.conf.d/50unattended-upgrades-107-//Acquire::http::Dl-Limit "70";
journalctl -u unattended-upgrades
Jul 10 07:52:31 PC systemd[1]: Started Unattended Upgrades Shutdown.
Jul 14 10:03:03 PC systemd[1]: unattended-upgrades.service: Succeeded.
-- Reboot --
Jul 14 10:04:11 PC systemd[1]: Started Unattended Upgrades Shutdown.
Jul 15 11:18:03 PC systemd[1]: unattended-upgrades.service:
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
You can use the 'fastboot' kernel parameter to bypass the systemd-fsckd issue. So overall most systems can work around the bug in full using kernel parameters: quiet splash loglevel=2 fastboot After that I've only encountered one weird laptop that refused to stay silent (even with loglevel=0). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051576] Re: Please merge 1.9.15p5-3 into noble
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/459624 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2051576 Title: Please merge 1.9.15p5-3 into noble Status in sudo package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2051576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
The userspace part of this bug is coming from our systemd patch: debian/fsckd-daemon-for-inter-fsckd-communication.patch In particular where systemd-fsckd.service says: StandardOutput=journal+console Is the patch still required at all, or can it be reordered to wait for Plymouth to splash first? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051672] Re: Sync iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main)
** Description changed: A few versions have been released and Ubuntu Noble still has the 6.1 version (6.1.0-1ubuntu2) from one year ago. Could it be possible to import the latest version from Debian unstable fixing a bunch of issues and supporting features from more recent kernels? Please note that Ubuntu Noble 24.04 will probably be shipped with the v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1 kernel, so missing the ones added to earlier versions. Switching to the v6.7 now should ease the upgrade to the v6.8 later. [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- the-24-04-noble-numbat-release/41958 + Upstream ChangeLog: + + - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/ + - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/ + - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/ + - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/ + - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/ + - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/ + + (Previous changelog: + https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22 + ) ChangeLog from Debian: iproute2 (6.7.0-2) unstable; urgency=medium - * Backport fix for 'ss' output + * Backport fix for 'ss' output - -- Luca Boccassi <> Mon, 22 Jan 2024 12:24:29 + + -- Luca Boccassi <> Mon, 22 Jan 2024 12:24:29 + iproute2 (6.7.0-1) unstable; urgency=medium - * Add Italian debconf translation (Closes: #1056582) - * Update upstream source from tag 'upstream/6.7.0' - * Bump copyright year ranges in d/copyright - * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch, - merged upstream - * Default config files moved from /usr/lib to /usr/share + * Add Italian debconf translation (Closes: #1056582) + * Update upstream source from tag 'upstream/6.7.0' + * Bump copyright year ranges in d/copyright + * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch, + merged upstream + * Default config files moved from /usr/lib to /usr/share - -- Luca Boccassi <> Fri, 12 Jan 2024 21:47:59 + + -- Luca Boccassi <> Fri, 12 Jan 2024 21:47:59 + iproute2 (6.6.0-1) unstable; urgency=medium - * Update upstream source from tag 'upstream/6.6.0' - * Backport patch to fix configuration installation - * Remove handling of qt_atm.so, dropped upstream + * Update upstream source from tag 'upstream/6.6.0' + * Backport patch to fix configuration installation + * Remove handling of qt_atm.so, dropped upstream - -- Luca Boccassi <> Sun, 05 Nov 2023 22:46:20 + + -- Luca Boccassi <> Sun, 05 Nov 2023 22:46:20 + iproute2 (6.5.0-5) unstable; urgency=medium - * Use dh-sequence-movetousr + * Use dh-sequence-movetousr - -- Luca Boccassi <> Tue, 24 Oct 2023 15:24:01 +0100 + -- Luca Boccassi <> Tue, 24 Oct 2023 15:24:01 +0100 iproute2 (6.5.0-4) unstable; urgency=medium - * postinst: handle legacy config files only when upgrading from previous - versions that shipped them - * postinst: ensure that locally modified legacy config files are - preserved as overrides on upgrade (Closes: #1051577) - * Note configuration files location changes in NEWS + * postinst: handle legacy config files only when upgrading from previous + versions that shipped them + * postinst: ensure that locally modified legacy config files are + preserved as overrides on upgrade (Closes: #1051577) + * Note configuration files location changes in NEWS - -- Luca Boccassi <> Sat, 16 Sep 2023 18:58:51 +0100 + -- Luca Boccassi <> Sat, 16 Sep 2023 18:58:51 +0100 iproute2 (6.5.0-3) unstable; urgency=medium - * Remove further leftovers as part of upstream's move of config to /usr - (Closes: #1051577) + * Remove further leftovers as part of upstream's move of config to /usr + (Closes: #1051577) - -- Luca Boccassi <> Mon, 11 Sep 2023 09:42:12 +0100 + -- Luca Boccassi <> Mon, 11 Sep 2023 09:42:12 +0100 iproute2 (6.5.0-2) unstable; urgency=medium - * Add maintscript to remove conffiles that upstream has moved to /usr - (Closes: #1051577) + * Add maintscript to remove conffiles that upstream has moved to /usr + (Closes: #1051577) - -- Luca Boccassi <> Sun, 10 Sep 2023 21:28:28 +0100 + -- Luca Boccassi <> Sun, 10 Sep 2023 21:28:28 +0100 iproute2 (6.5.0-1) unstable; urgency=medium - [ Luca Boccassi ] - * Use wildcard for Lintian overrides + [ Luca Boccassi ] + * Use wildcard for Lintian overrides - [ Peter Kvillegård ] - * Add Swedish translation of debconf messages (Closes: #1050442) + [ Peter Kvillegård ] + * Add Swedish translation of debconf messages (Closes: #1050442) - [ Luca Boccassi ] - * Update upstream
[Touch-packages] [Bug 2051672] [NEW] Sync iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main)
Public bug reported: A few versions have been released and Ubuntu Noble still has the 6.1 version (6.1.0-1ubuntu2) from one year ago. Could it be possible to import the latest version from Debian unstable fixing a bunch of issues and supporting features from more recent kernels? Please note that Ubuntu Noble 24.04 will probably be shipped with the v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1 kernel, so missing the ones added to earlier versions. Switching to the v6.7 now should ease the upgrade to the v6.8 later. [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- the-24-04-noble-numbat-release/41958 Upstream ChangeLog: - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/ - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/ - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/ - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/ - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/ - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/ (Previous changelog: https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22 ) ChangeLog from Debian: iproute2 (6.7.0-2) unstable; urgency=medium * Backport fix for 'ss' output -- Luca Boccassi <> Mon, 22 Jan 2024 12:24:29 + iproute2 (6.7.0-1) unstable; urgency=medium * Add Italian debconf translation (Closes: #1056582) * Update upstream source from tag 'upstream/6.7.0' * Bump copyright year ranges in d/copyright * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch, merged upstream * Default config files moved from /usr/lib to /usr/share -- Luca Boccassi <> Fri, 12 Jan 2024 21:47:59 + iproute2 (6.6.0-1) unstable; urgency=medium * Update upstream source from tag 'upstream/6.6.0' * Backport patch to fix configuration installation * Remove handling of qt_atm.so, dropped upstream -- Luca Boccassi <> Sun, 05 Nov 2023 22:46:20 + iproute2 (6.5.0-5) unstable; urgency=medium * Use dh-sequence-movetousr -- Luca Boccassi <> Tue, 24 Oct 2023 15:24:01 +0100 iproute2 (6.5.0-4) unstable; urgency=medium * postinst: handle legacy config files only when upgrading from previous versions that shipped them * postinst: ensure that locally modified legacy config files are preserved as overrides on upgrade (Closes: #1051577) * Note configuration files location changes in NEWS -- Luca Boccassi <> Sat, 16 Sep 2023 18:58:51 +0100 iproute2 (6.5.0-3) unstable; urgency=medium * Remove further leftovers as part of upstream's move of config to /usr (Closes: #1051577) -- Luca Boccassi <> Mon, 11 Sep 2023 09:42:12 +0100 iproute2 (6.5.0-2) unstable; urgency=medium * Add maintscript to remove conffiles that upstream has moved to /usr (Closes: #1051577) -- Luca Boccassi <> Sun, 10 Sep 2023 21:28:28 +0100 iproute2 (6.5.0-1) unstable; urgency=medium [ Luca Boccassi ] * Use wildcard for Lintian overrides [ Peter Kvillegård ] * Add Swedish translation of debconf messages (Closes: #1050442) [ Luca Boccassi ] * Update upstream source from tag 'upstream/6.5.0' * Use cap_bpf instead of cap_sys_admin for ip vrf-exec * Package-provided config files are now shipped in /usr/iproute2 instead of /etc/iproute2 -- Luca Boccassi <> Sat, 09 Sep 2023 16:32:54 +0100 iproute2 (6.4.0-1) unstable; urgency=medium * Fix patch header Forwarded field * Enable ELF metadata stamping * Update upstream source from tag 'upstream/6.4.0' * Update Lintian overrides -- Luca Boccassi <> Fri, 30 Jun 2023 12:16:40 +0100 iproute2 (6.3.0-1) unstable; urgency=medium * Drop obsolete conflicts/replaces * Update upstream source from tag 'upstream/6.3.0' -- Luca Boccassi <> Tue, 13 Jun 2023 23:49:37 +0100 iproute2 (6.1.0-3) unstable; urgency=medium * Ensure 'ip mo' resolves to 'ip monitor' (Closes: #1036534) -- Luca Boccassi <> Mon, 22 May 2023 14:19:52 +0100 iproute2 (6.1.0-2) unstable; urgency=medium * Add Romanian language translation for debconf (Closes: #1031917) * Bump Standards-Version to 4.6.2, no changes * Bump d/copyright year range -- Luca Boccassi <> Sat, 25 Feb 2023 19:46:35 + ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: Sync iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main) Status in iproute2 package in Ubuntu: New Bug description: A few versions have been released and Ubuntu Noble still has the 6.1 version (6.1.0-1ubuntu2) from one year ago. Could it be possible to import the latest version from Debian unstable fixing a bunch of issues and supporting
